-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Add a /current route that we can use in various places #185
Comments
It could be implemented by sorting projectVersions with something like https://github.com/ragingwind/semver-sort. But maybe it would be better to sort it already in jsonapi-docs project. It would probably be more efficient. |
we already have an array of sorted versions based on semver. We just need to handle |
It does not seem to be sorted here: https://ead-sk.global.ssl.fastly.net/rev-index/ember.json. Maybe I am looking at a wrong place? |
Oh its done part of the app in that route's controller |
I see, that's great then. I will use that :). Probably will have to move it to the model though. |
Would be cool instead of or in addition to |
Hopefully /current and /release are the same. |
correct, though I feel like "release" would be clearer to what "current" means. Current could mean canary or beta or lts as well. |
Maybe we should reopen this? I will revisit this once the route structure refactor is merged. |
…ly-warnings fixing Netlify warnings
At times we need the ability to link to "the most current" version of api docs (see #184 for an example). We need to add a
/current
route to this Ember app that will display the most current version of the api docs.The text was updated successfully, but these errors were encountered: