IMO, if this is the setup you want, we should just implement it server-side and not worry about hacking text parsing into the client side. 

I'm still not sold on it, though. When I write lists, I like to have the flexibility afforded by raw text. For example, adding sub-lists, numbered vs bulleted, etc.  My vote is still to keep the plain text field, but add something like markdown support or something 

Justin
mutter.justin@gmail.com
613.884.4495

Brought to you by the power of iPhone.

On 2013-05-19, at 2:41 PM, Julian Nadeau <notifications@github.com> wrote:

> In Testasaurus Rex/Testasaurus Rex/Controllers/TREXTestCaseController.m:
> 
> >  {
> > -	TREXStepsTableViewCell *tableViewCell = (TREXStepsTableViewCell*)cell;
> > -	NSInteger idx = [tableViewCell tag];
> > -	if (idx < [_steps count]) {
> > -		[_steps removeObjectAtIndex:idx];
> > +	TREXStepsTableViewCell *tableViewCell = (TREXStepsTableViewCell*)tableCellView;
> > +	NSTableView *tableView = (NSTableView*)tableCellView.superview.superview;
> > +	
> > +	if ([tableView isEqual:_stepsTableView]) {
> > +		NSInteger idx = [tableViewCell tag];
> > +		if (idx < [_steps count]) {
> > +			[_steps removeObjectAtIndex:idx];
> I can look at bringing this over to the model, but if my intentions work as desired, I will be refactoring and migrating the steps into a one to many relationship with a test case. In this sense, I'm not sure if I should be worrying about this right now.
> 
> —
> Reply to this email directly or view it on GitHub.