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

Deprecate implicit record loading in Ember Route #774

Merged
merged 13 commits into from
Feb 3, 2023

Conversation

snewcomer
Copy link
Contributor

@snewcomer snewcomer commented Nov 14, 2021

Rendered

close #773
close #557

@snewcomer snewcomer self-assigned this Nov 14, 2021
@snewcomer snewcomer force-pushed the implicit-record-route branch 2 times, most recently from d1c1eee to fc0f0f1 Compare November 14, 2021 13:32
text/0774-implicit-record-route-loading.md Outdated Show resolved Hide resolved
text/0774-implicit-record-route-loading.md Outdated Show resolved Hide resolved
text/0774-implicit-record-route-loading.md Outdated Show resolved Hide resolved
text/0774-implicit-record-route-loading.md Outdated Show resolved Hide resolved
text/0774-implicit-record-route-loading.md Outdated Show resolved Hide resolved
@wagenet
Copy link
Member

wagenet commented Jul 23, 2022

@scottmessinger @runspired is there anything more that we need here other than an "official" review?

@runspired
Copy link
Contributor

@wagenet this is a framework team item not a data team item though Scott did pick it up from @NullVoxPopuli it seems to try to get it over the line. I think this became of increased importance because the troll behavior lead to increased bug reports and confusion once injections were eliminated for 4.x

@NullVoxPopuli
Copy link
Contributor

ah right! this supersedes #557 <-- I'll close this

@snewcomer
Copy link
Contributor Author

100%. I’d be eager to do the legwork once merged if someone else didn’t pick it up. Unsure if it needs a “sponsor”. Let me know if someone can bring it up in the core team meeting!

@ef4
Copy link
Contributor

ef4 commented Aug 5, 2022

Framework core discussed this and everyone is in favor of the deprecation.

A suggestion is that the design could use an optional feature that disables the old bad behavior. This would let people clear the deprecation by enabling the feature, rather than requiring them to create new empty model hooks and potentially new route files.

@snewcomer
Copy link
Contributor Author

@ef4 hi! Any updates on this RFC?

@wagenet
Copy link
Member

wagenet commented Nov 8, 2022

@snewcomer looks like it may have gotten dropped on accident, sorry! I've officially added it to the agenda for our next meeting.

@wagenet wagenet added the S-Proposed In the Proposed Stage label Dec 2, 2022
@wagenet wagenet added S-Exploring In the Exploring RFC Stage and removed S-Proposed In the Proposed Stage labels Jan 13, 2023
@wagenet
Copy link
Member

wagenet commented Jan 13, 2023

@snewcomer Sorry for the delay. Everything got thrown off with the holidays. I'll try to get this back on track.

@wagenet
Copy link
Member

wagenet commented Jan 27, 2023

We agreed to move this to FCP. It needs a few tweaks for our new stages setup and will need to be retargeted at v6. I can help with this.

@wagenet wagenet assigned wagenet and unassigned locks and snewcomer Jan 27, 2023
@wagenet
Copy link
Member

wagenet commented Jan 27, 2023

Relatedly, we should also deprecate the default store property in routes.

Copy link
Member

@wagenet wagenet left a comment

Choose a reason for hiding this comment

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

Looks good! In addition to the inline comments, can you add a "Drawbacks" section? I think it's sufficient to just note that when the implicit behavior is nice it saves typing and now you have to type more.

text/0774-implicit-record-route-loading.md Outdated Show resolved Hide resolved
text/0774-implicit-record-route-loading.md Show resolved Hide resolved
@Windvis
Copy link

Windvis commented Jan 28, 2023

I think this also means that the routes-segments-snake-case rule can be removed from the recommended ruleset?

I've been disabling that rule on every project I work on since we don't depend on the implicit record loading and it would be nice if we could remove it from our eslint config file 😄.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deprecate default store and record loading in Ember route
9 participants