StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POBackbone.js modify newly fetched collection before reset events occur
primarykey
Id
15375688
data
AcceptedAnswerId
15441902
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-13T01:53:22.703
FavoriteCount
0
LastActivityDate
2013-03-15T21:22:01.603
LastEditDate
2013-03-15T20:51:05.440
LastEditorUserId
1169948
OwnerUserId
1169948
ParentId
0
PostTypeId
1
Score
1
ViewCount
879
LastEditorDisplayName
text
Body
I'm trying to do the following: <ol> <li>Fetch data from the server</li> <li>Add a zero-based index to the models before the views are notified</li> <li>Finally run have the 'render' events fire for the views</li> </ol> I was trying to do this by using a success callback in the collection View Before <pre><code>initialize: () -> @collection.on 'reset', @render, this render: () -> ...render code... </code></pre> Collection Before <pre><code>search: () -> @fetch { success: @fetch_success } fetch_success: () -> for i in [0...collection.models.length] collection.models[i].set('go_index', i) </code></pre> Doing things this way was causing the views to fire their render events before the collection was updated by the success callback. The solution I came up with was to have the views listen to a <code>fetched</code> event, then have the collection fire that after it successfully modifies the collection: View After <pre><code>initialize: () -> @collection.on 'fetched', @render, this render: () -> ...render code... </code></pre> Collection After <pre><code>initialize: () -> @on 'reset', @add_index_and_notify, this add_index_and_notify: () -> for i in [0...@models.length] @models[i].set('go_index', i) @trigger('fetched') </code></pre> This works fine, I'm just wondering if this is the most elegant way to accomplish this or if there is a built-in way that I'm missing. UPDATE 3/15 I've come up with a cleaner solution that doesn't require the view to do any of the dirty work and I don't have to create a custom event. The trick is to listen to the <code>sync</code> event (which fires after <code>reset</code>) View Final <pre><code>initialize: () -> @collection.on 'sync', @render, this render: () -> ...render code... </code></pre> Collection Final <pre><code>initialize: () -> @on 'reset', @add_index, this add_index: () -> for i in [0...@models.length] @models[i].set('go_index', i) </code></pre> Hopefully this pattern can help somebody searching in the future.
Tags
<backbone.js><backbone-views><backbone-events>
Title
Backbone.js modify newly fetched collection before reset events occur
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDan Caddigan
UserOwnerUserId
1. USDan Caddigan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POBackbone.js modify newly fetched collection before reset events occur
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.