-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Tabs2 ➡️ Tabs #1900
Tabs2 ➡️ Tabs #1900
Conversation
@@ -1,5 +1,5 @@ | |||
/* | |||
* Copyright 2015 Palantir Technologies, Inc. All rights reserved. | |||
* Copyright 2017 Palantir Technologies, Inc. All rights reserved. |
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.
🤔 original date?
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'm down to leave the original date.
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 like to use 2015-present
since it's never out of date
export const Home = () => <Tabs selectedTabIndex={0}>{contents}</Tabs>; | ||
export const Projects = () => <Tabs selectedTabIndex={1}>{contents}</Tabs>; | ||
export const Home = () => <Tabs selectedTabId="home">{contents}</Tabs>; | ||
export const Projects = () => <Tabs selectedTabId="projects">{contents}</Tabs>; |
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.
@adidahiya are these updates correct? is this section still useful?
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.
hmm, we should probably remove this react router section because it probably doesn't work with react-router v4. we can add it back if requested by users.
and fix all the *other* usagesPreview: documentation |
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.
prefer to wait on #1885 and deal with merge conflicts here rather than there
@adidahiya - waited, resolved merged conflicts. |
copyright yearPreview: documentation |
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.
lgtm, just remove the react-router part
export const Home = () => <Tabs selectedTabIndex={0}>{contents}</Tabs>; | ||
export const Projects = () => <Tabs selectedTabIndex={1}>{contents}</Tabs>; | ||
export const Home = () => <Tabs selectedTabId="home">{contents}</Tabs>; | ||
export const Projects = () => <Tabs selectedTabId="projects">{contents}</Tabs>; |
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.
hmm, we should probably remove this react router section because it probably doesn't work with react-router v4. we can add it back if requested by users.
you probably need to merge master to fix the overlay test flake. |
Merge branch 'master' of github.com:palantir/blueprint into gg/tabsPreview: documentation | table |
Tabs2
replaces originalTabs
API.