-
-
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
Reintroduce "Handle /release requests" #239
Reintroduce "Handle /release requests" #239
Conversation
@mschinis will this be ok to have with regards to algolia indexing? |
@sivakumar-kailasam yep, I believe we can ignore specific paths as adding both |
I'm for leaving out |
@MartinMalinda are you going to redirect |
@mschinis Probably not so far. So far I am not convinced we should do that. This PR actually goes a little bit into opposite direction. If you visit I'm open to other suggestions here though. I can be wrong. |
@mschinis if we're in a particular version of docs and if we start performing an aloglia search, are results shown to the current version's docs first? +1 on not redirecting to specific versions since too many redirects night penalize us on SEO. On a totally unrelated note I tried reaching existing api path structures on api-beta and whatever I tried redirected as expected. |
Agreed on keeping the url the same, but we need to make sure we get this right, as it can actually screw up with SEO. If @sivakumar-kailasam yes, the search should only search through the version in the URL, so we might actually need to get algolia to also scrape the current URL. In my previous message above, I thought we were only going to redirect, hence why I mentioned we could ignore specific URLs. |
@mschinis there was an idea to have |
Ok, it seems like it is possible to populate headData from the metaStore, which contains project versions. So conditional rendering of |
@MartinMalinda can you rearrange your commits a bit to get a cleaner history? |
4b0ba74
to
faadfa0
Compare
@MartinMalinda I'm going to add |
@mschinis I have the canonical URL mostly done, I'm just improving test coverage. Can refactor it later though. |
canonicalURL works now, but there is an issue when |
I think this is almost ready to merge. The only thing missing is test coverage for canonicalURL which is hard to do without mirage or any other backend mock. But I'll give it some more thought. |
Seems like the only proper way to test the canonicalURL is to use https://github.com/kaliber5/ember-fastboot-app-tests. |
@MartinMalinda do you mind resolving conflicts? I'd like to get this reviewed/tested. |
12b8d4f
to
3d4343d
Compare
return checkLinks('attributes', '.attributes a', versionString); | ||
}; | ||
|
||
let checkIndexListLinks = versionString => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not a big deal but this could also be written as,
let checkIndexListLinks = (versionString) => checkLinks('index-list', '.api-index-filter a', versionString);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 will change that unless the line is too long
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah this is fine :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just changed it :D it made me notice this flaw here f37e79d#diff-b409b67c33eb7131aee5de1bebe70e5bR14 at least. Passed selector
variable was actually not used in the helper function.
app/models/project-version.js
Outdated
return this.get('project.latestProjectVersion.id') === this.get('version'); | ||
}), | ||
|
||
isLTS: computed(function() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missed linking to version
in the computed definition
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version on project-version model does not change, but maybe I should add it anyway for clarity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah that makes sense. Missed the context there :)
we ended up taking a slightly different approach, but currently have release supported. What we still need to do is add a feature that puts canonical to release in each non-release page. May need some thought on how to do this for pre-2.16 versions that don't match names/modules. |
rel=canonical
meta to pages with versions that matchrelease
orlts