-
-
Notifications
You must be signed in to change notification settings - Fork 113
WIP bugfix: hide private API when following guides/legacy links (#307) #339
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
Conversation
This would kill people's bookmarks |
@toddjordan because people have bookmarks that include the QPs? I'll read this a little more closely and see if I can account for those. |
Yes people have bookmarks to private things. I guess it's a question of whether to support it |
Broken links are the worst. I didn't really think it through all the way, just saw that legacy links get all the boxes checked and that the Guides are linking people to private APIs. I'll give it another shot. I think I can JavaScript my way through supporting both. |
Yeah. Agreed it's confusing linking from guides. We should def. convert thing guide links to the new URL structure |
@toddjordan I think maybe this fixes it? Let me know your thoughts. As of my latest commit:
Examples: Legacy hashed link without QP: http://localhost:4200/classes/Ember.Router.html?e#method_map Legacy links without a hash or QP: http://localhost:4200/classes/String.html Legacy links with QP and without a hash: http://localhost:4200/classes/String.html?show=private Legacy private API links with private QP: http://localhost:4200/classes/Ember.Router.html?show=private#method__deserializeQueryParam Legacy private API links missing QP: http://localhost:4200/classes/Ember.Router.html#method__deserializeQueryParam |
@toddjordan I also experimentally tried to fix #340 |
I just realized I am making the assumption that the old API site used QPs and they were named the same. Is that true? |
I'm just going to close this and do something totally different after the links have settled. It's partially irrelevant from replacing all the links in 2.16 guides |
Fixing index.md files for 1.12
WIP don't merge.
Addresses #307
Based on conversation about hiding private API by default (#303), I think it makes sense that legacy urls should not show private api by default either.
Currently, links from the Guides redirect to showing all QPs (inherited, protected, private, deprecated), so new learners would see private API a lot. I fixed this by changing the legacy url processing.