Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8302929
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T17:24:16+00:00 2026-06-08T17:24:16+00:00

If I have a deeply-nested model graph, coming from the server (a lot of

  • 0

If I have a deeply-nested model graph, coming from the server (a lot of children objects, some of which arrays). Is it a good practice to turn each of the children of the object, into Models and Collections respective, when I turn the object into a Model? This will be handy because it will reduce the confusion of what should be called how. For example, it is much clearer to have something like that:

myModel.get("child1").get("collection1").get(0);

instead of:

myModel.get("child1").collection1[0];

On another side, it might turn into a performance hell if we are trying to convert these at runtime, especially if the object graph is really deep.

What is the best practice there?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T17:24:17+00:00Added an answer on June 8, 2026 at 5:24 pm

    You should use Backbone.relational to take care of it for you.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have some deeply randomly nested dictionary as follows. {'CompilationStatistics': {'CodeGeneration': {'EndTime': '2010-04-21T14:03:11', 'StartTime':
Suppose we have to use in some function deeply nested pointer very extensively: function
I have a page with deeply-nested HTML elements generated from a framework. I would
Let's say I have some deeply nested markup that I want to target with
I have a particular element (input box) that's deeply nested in some table stuff
I have a deeply nested for-comprehension, simplified to 3 levels below: x, y, and
Thanks in advance for your time. I have a deeply nested XML whose XSLT
I have this deeply nested list (list of lists) and I want to replace
I have a deeply nested partial view, where I iterate over a collection of
I have a several nested methods in my program. If a deeply nested method

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.