-
Notifications
You must be signed in to change notification settings - Fork 69
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
[New Theme] Rename to Next
#835
[New Theme] Rename to Next
#835
Conversation
@@ -9,10 +9,7 @@ | |||
* GitHub history for details. | |||
*/ | |||
|
|||
// sass-lint:disable no-url-domains, no-url-protocols | |||
@import url('https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&family=Roboto+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap'); |
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.
Should this be replaced with Source Sans & Source Code fonts?
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.
Yeah, good question - @AMoo-Miki I understand we're not packaging the new fonts with OUI, but do we want to do the same thing where we hot link for the purpose of the doc site?
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.
Yep! i knew i forgot something. Thanks.
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.
To note: here, this is to enable the fonts on the docsite, not to package the fonts with OUI. OUI doesn't package any fonts out of the box, that is up to the implementor
@@ -9,10 +9,7 @@ | |||
* GitHub history for details. | |||
*/ | |||
|
|||
// sass-lint:disable no-url-domains, no-url-protocols | |||
@import url('https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&family=Roboto+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap'); |
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.
Same as previous comment
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 some minor questions, but looks good.
@@ -9,10 +9,7 @@ | |||
* GitHub history for details. | |||
*/ | |||
|
|||
// sass-lint:disable no-url-domains, no-url-protocols | |||
@import url('https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&family=Roboto+Mono:ital,wght@0,400;0,700;1,400;1,700&display=swap'); |
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.
Yeah, good question - @AMoo-Miki I understand we're not packaging the new fonts with OUI, but do we want to do the same thing where we hot link for the purpose of the doc site?
import { ThemeContext } from '../../components'; | ||
|
||
export default () => { | ||
const themeContext = useContext(ThemeContext); |
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.
What is the theme context, and do we still use it elsewhere?
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 guy is responsible for switching between light and dark themes. I donno how we switch from default to "Next" in the docs but will figure it out.
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.
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.
Also, theme context is responsible for switching between themes in general on docsite, not just light/dark
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.
Matt is right; for OUI, light, dark, next-light, and next-dark are individual themes.
e44d5b5
to
04466e2
Compare
<OuiCode>hasShadow</OuiCode>. The default theme only allows | ||
removing the border if both <OuiCode>hasShadow</OuiCode> and{' '} | ||
and/or shadow. The default theme only allows removing the border | ||
if both <OuiCode>hasShadow</OuiCode> and{' '} |
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.
Are we renaming cascadia
theme to next
or is it a different theme altogether (default theme)?
I see difference in the comment here. Is it intended?
The Cascadia theme doesn't allow combining the{' '}
<OuiCode>hasBorder</OuiCode> option with{' '}
<OuiCode>hasShadow</OuiCode>.
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.
cas* was a temporary reference to a temporary and incomplete theme; that was reset to default in #816. The new colors are just named "Next"
|
||
import { OuiPanel, OuiCode, OuiSpacer } from '../../../../src/components'; | ||
import { ThemeContext } from '../../components'; | ||
|
||
export default () => { |
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.
Does it mean we have only one theme now (default one)? and do not need theme context anymore to determine the theme?
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 previous beta theme had limitations and ThemeContext
was used to apply rules when dealing with those limitations. Next is evolved out of default and as such, has none of those limitations so. there was no need to know the ThemeContext
in this file.
04466e2
to
3c72650
Compare
Also: * Show the Next theme in the docsite Signed-off-by: Miki <miki@amazon.com>
3c72650
to
c7f7c70
Compare
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! Thank you for the change.
Also: * Show the Next theme in the docsite (cherry picked from commit 0365b42) Signed-off-by: Miki <miki@amazon.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
This renames the file and references to the old name.
Also, certain comments that talk about the old beta theme's specifications or limitations are reworded or removed. There are 2 instances that more information is needed before removing some logic.
Check List
yarn lint
yarn test-unit
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.