-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: Deprecate And Remove Spree.routes #3405
Comments
Now that we have this issue, someone with permissions can close #2113. |
seand7565
added a commit
to seand7565/solidus
that referenced
this issue
May 4, 2020
This PR replaces all instances of Spree.routes with Spree.pathFor. Spree.routes still exists, we're just preferring to use Spree.pathFor per solidusio#3405.
5 tasks
seand7565
added a commit
to seand7565/solidus
that referenced
this issue
May 12, 2020
This PR replaces all instances of Spree.routes with Spree.pathFor. Spree.routes still exists, we're just preferring to use Spree.pathFor per solidusio#3405.
seand7565
added a commit
to seand7565/solidus
that referenced
this issue
May 12, 2020
This PR replaces all instances of Spree.routes with Spree.pathFor. Spree.routes still exists, we're just preferring to use Spree.pathFor per solidusio#3405.
seand7565
added a commit
to seand7565/solidus
that referenced
this issue
May 12, 2020
This PR replaces all instances of Spree.routes with Spree.pathFor. Spree.routes still exists, we're just preferring to use Spree.pathFor per solidusio#3405.
seand7565
added a commit
to seand7565/solidus
that referenced
this issue
May 13, 2020
This PR replaces all instances of Spree.routes with Spree.pathFor. Spree.routes still exists, we're just preferring to use Spree.pathFor per solidusio#3405.
seand7565
added a commit
to seand7565/solidus
that referenced
this issue
May 16, 2020
This PR replaces all instances of Spree.routes with Spree.pathFor. Spree.routes still exists, we're just preferring to use Spree.pathFor per solidusio#3405. It uses Proxy to issue a deprecation warning, however if Proxy isn't defined (in older browsers like IE) will just return the routes without deprecation. Hopefully the developer of the app will have something newer than IE, if they don't I imagine they have bigger problems than JS route deprecations 😬 Also adds Proxy to ESlint so it doesn't trigger the no-undef rule.
seand7565
added a commit
to seand7565/solidus
that referenced
this issue
May 22, 2020
This PR replaces all instances of Spree.routes with Spree.pathFor. Spree.routes still exists, we're just preferring to use Spree.pathFor per solidusio#3405. It uses Proxy to issue a deprecation warning, however if Proxy isn't defined (in older browsers like IE) will just return the routes without deprecation. Hopefully the developer of the app will have something newer than IE, if they don't I imagine they have bigger problems than JS route deprecations 😬 Also adds Proxy to ESlint so it doesn't trigger the no-undef rule.
#3605 is merged and should close this issue! 🎉 |
mamhoff
pushed a commit
to mamhoff/solidus
that referenced
this issue
Feb 1, 2021
This PR replaces all instances of Spree.routes with Spree.pathFor. Spree.routes still exists, we're just preferring to use Spree.pathFor per solidusio#3405. It uses Proxy to issue a deprecation warning, however if Proxy isn't defined (in older browsers like IE) will just return the routes without deprecation. Hopefully the developer of the app will have something newer than IE, if they don't I imagine they have bigger problems than JS route deprecations 😬 Also adds Proxy to ESlint so it doesn't trigger the no-undef rule.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As documented in #2113, the route helpers in
Spree.routes
are poorly and inconsistently named. Hawth also stopped using them in new admin code, instead preferring to usepathFor
directly. As mentioned in #2113, this is a pretty low priority issue, but making a decision allows us to close the old issue and move on with a solution.Solution:
Deprecate
Spree.routes
and replace all uses of it withpathFor
. Remove it in a future major version. I prefer this solution becauseSpree.routes
doesn't provide much value and is a small burden to keep up to date.Alternative:
Warn users that we will be making
Spree.routes
consistent with the Rails route naming. Update all the names in the next major version. Given that this is still a breaking change, I'm less a fan of it, but if people truly findSpree.routes
valuable, then I'm not opposed to keeping it.The text was updated successfully, but these errors were encountered: