Create element in default position

[csaura]

When I try create a new element in the default position create it at the bottom of the list.

Example:

*********************************
* Tasks
*********************************
* id
* name
* position , NOT NULL, DEFAULT 0
*********************************

class Task
 acts_as_list  top_of_list: 0, add_new_at: :bottom
end

# existing elements
task position: 0 id: 20
task position: 1 id: 35
task position: 2 id: 15
task position: 3 id: 14
task position: 4 id: 16
task position: 5 id: 17
task position: 6 id: 18

# create new element
task = Task.create(position: 0, name: 'I want to be at the top')

task.position => 7 # but I wanted to create it at position 0

How can I create a new element forcing the default position?

[csaura]

Do you think make sense to create a new method to force the top position?

[swanandp]

:add_new_at :bottom will override position: 0

[swanandp]

Actually no, what I said is not right.

[swanandp]

Can you try

task = Task.build(name: 'I want to be at the top')
task.insert_at(0)

[danascheider]

I am having this same issue. :add_new_at does seem to override any sort of manual positioning. In my case, I have:

class Task 
  belongs_to :task_list
  acts_as_list scope: :task_list, add_new_at: :top    # top position in this case is 1
end

I'm trying to add slightly more complicated logic for default list positions:

• By default, most tasks are created at position 1
• If a task's status is changed to 'complete', it should go to the bottom of the list
• If a task is created with status 'complete', it should be the first complete task

I have the first 2 under control; the 3rd one is causing me the same problem csaura is having. I've tried effecting the behavior through before_create callbacks, after_create callbacks, and by modifying the model's :create! method. None of these has had any impact whatsoever. I also tried what you suggested in your last post, and that didn't change anything either.

[brendon]

Joining in late, but this sounds like two different scopes to me.

acts_as_list scope: [:task_list, :status], add_new_at: :top

or something like that. Still that wouldn't allow for the complex logic about where in the list an item in the complete status scope should go when it joins that scope. Callbacks are probably the answer, or manually specifying the position after checking the existing entries.

I'll close this for now since it's had no action for a while, but I'm happy to discuss it further if you want.