Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Version 3] What to do with missing belongsTo relationships #80

Open
frederikbosch opened this issue Nov 16, 2018 · 0 comments
Open

[Version 3] What to do with missing belongsTo relationships #80

frederikbosch opened this issue Nov 16, 2018 · 0 comments

Comments

@frederikbosch
Copy link
Contributor

frederikbosch commented Nov 16, 2018

During the upgrade I did find out some things.

  1. There is code within Ember Data that is focussing on this topic.
  2. That code did fire during the upgrade of this addon to 3.0-betaX for has many relationships, but not for belongsTo. I have no idea why it did not. As my own app was not having troubles by it, I was OK with it. At least, temporarily.
  3. So let's accept that missing hasMany relationships will lead to a rejection when fetching the relationship.
  4. What to do with belongsTo? Is there any convention within Ember Data? If not, what would be our best guess with regard to offline applications? Or maybe a setting?
  5. First let's open an issue here that describes our thinking, then open issue at Ember Data for clarification.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant