On Monday, October 21, 2013 4:37:22 PM UTC+1, Neil Williams wrote:
Hi Fred,
Thanks for your reply.
Using new in this way isn't something I've come across in quite a few
years of using rails.
How would you initialise a new Task object given you have the @story
instance available to
Hi Fred,
Thanks for this.
yes I can understand why it has never been a problem. It won't be too much
of a problem for us either, as the collection variable e.g. @tasks, would
normally be filtered with .where() or be ordered with .order(), therefore,
they would be different instances. But I
On Monday, October 21, 2013 11:28:22 AM UTC+1, Neil Williams wrote:
Hi All,
I have been told to post discussion based topic on here instead of the
GitHub Issues.
I thought this 'could' be a bug, but just need some clarification really.
The issue I posted is here
Hi Fred,
Thanks for your reply.
Using new in this way isn't something I've come across in quite a few
years of using rails.
How would you initialise a new Task object given you have the @story
instance available to you?
@task = Task.new(:story_id = @story.id)?
If the above, I really
4 matches
Mail list logo