-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Multi version docsite #15692
Multi version docsite #15692
Conversation
`/pr-deploy-site/${process.env.BUILD_SOURCEBRANCH}/react-northstar/` | ||
: '/'; | ||
|
||
if (process.env.OFFICIALRELEASE) { |
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.
I might not need process.env.OFFICIALRELEASE
but I need to find out how/where process.env.PR_DEPLOY
is set
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.
using this env variable would still give us an easy way to build docsites for single versions
@@ -0,0 +1,116 @@ | |||
<!DOCTYPE html> |
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.
Any cleaner naming for this file ?
packages/fluentui/docs/src/components/Sidebar/VersionDropdown.tsx
Outdated
Show resolved
Hide resolved
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 1267d8d:
|
displayName: 'Publish docsite as pipeline artifact' | ||
inputs: | ||
PathtoPublish: 'packages/fluentui/docs/dist' | ||
ArtifactName: 'docsite_v$(docsiteVersion)' |
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.
Is it required?
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.
no, I think but it's handy to have the artifacts available... storage is cheap and we can backfill easily if we ever move storage or have to clean it for some reason
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: eb0f2c4b76a921fa9a8b069189ecdacff7029117 (build) |
@@ -486,6 +487,7 @@ const Sidebar: React.FC<RouteComponentProps & SidebarProps> = props => { | |||
> | |||
Fluent <span style={gradientTextStyles}>UI</span> | |||
</Text> | |||
<VersionDropdown width={props.width} /> |
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.
<VersionDropdown width={props.width} /> | |
{process.env.NODE_ENV === 'production' && <VersionDropdown width={props.width} />} |
So we hide this during local builds?
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.
This is should already be covered in the component itself, although you reminded me that I have no catch
for the fetch.... is that enough for you or should we be more explicit to not render this locally at all ? It might be necessary to locally host a manifest to display this dropdown if you're working on it (like I have)
* Dropdown and shell for multi version docsite * Add deployment artifacts and config * PR fixes * revert yarn build * Add existing semver version in repo to docs * Fix basepath * added changelog entry * fix changelog entry * fixed parentheses in changelog * add dependency for versiondropdown * Use compare-versions to validate semver
Pull request checklist
$ yarn change
Description of changes
Adds multi version support to the current N* docsite
Focus areas to test
(optional)