-
-
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
EmberObject returns 404 #704
Comments
I cannot reproduce 🤔 |
Tried throttling to slow 3G and hard reloading. Still unable to reproduce. 😥 |
OK. Can reproduce by blocking domain https://api-store.emberjs.com I'll assume the user was not able to connect to the domain but that fastboot was working, so it looks like all is well until he clicks any link, including EmberObject. @sivakumar-kailasam @locks @toddjordan @jenweber What sort of "more correct" error message should we show, or should we leave the 404 alone? |
This was actually more limited in scope - just this link (that I had tried) was not working. I had been all around various Ember and Ember Data APIs before encountering this one. I actually first encountered it while trying to get to EmberObject from an inherits reference. Seems to be resolved on an incognito window, so maybe a cache issue. |
Ok, these 404 issues can obviously have multiple causes. @benmurden You may have experienced a problem that could have been reproduced by the steps @alexeykostevich provided in #672 |
Yes, the steps in #701 (comment) reproduce the issue for me. |
@benmurden Is the issue fixed for you? |
@Gaurav0 The issue is fixed for Ember project links, but if I switch to Ember Data under Projects, all the links on the right return 404 with console errors like the following.
I suspect the right pane should have changed to something else after clicking Ember Data. |
https://api.emberjs.com/ember/release
This page has a link to EmberObject that points to the following URL
https://api.emberjs.com/ember/release/classes/EmberObject
however, this returns a 404 error.
The text was updated successfully, but these errors were encountered: