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

rfc: ember-data | deprecate-non-strict-types #740

Merged

Conversation

runspired
Copy link
Contributor

@runspired runspired commented Apr 24, 2021

Full Text: Rendered

@runspired runspired added T-ember-data RFCs that impact the ember-data library T-deprecation labels Apr 24, 2021
Copy link
Member

@hjdivad hjdivad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

definitely LGTM. Thanks for driving this @runspired

Comment on lines +16 to +18
Deprecates when the `type` for a record provided by a user differs from the resolved
type, thereby removing the need to configure `ember-inflector` to treat `types` as `uncountable`
in order to use plural model names, and removing the dasherization constraint.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd recommend clarifying what "resolved" means in this context.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The resolved type means the on-disk file-path derived type. So for instance a model at app/models/foos/otherUsers.js has the resolved type foos/otherUsers while app/models/foos/bar-user.js has the resolved type foos/bar-user. For the latter example, foos/barUser and foos/barUsers could both currently be supplied to ember-data in most contexts today and still result in a successful lookup of the model. Said uses would be required to be refactored to use the resolved type.

I'll try to add a note to this effect to the RFC for clarification.

@runspired runspired merged commit 6c42f8e into emberjs:master Jul 24, 2022
@runspired runspired self-assigned this Jul 31, 2022
runspired added a commit that referenced this pull request Sep 22, 2023
Advance RFC #740 `"EmberData | Deprecate Non Strict Types"` to Stage Ready for Release
runspired added a commit that referenced this pull request Sep 24, 2023
Advance RFC #740 `"EmberData | Deprecate Non Strict Types"` to Stage Released
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Final Comment Period T-deprecation T-ember-data RFCs that impact the ember-data library
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants