2019-09-20 04:27:57 -05:00
# Theming Grafana
2019-07-03 02:50:42 -05:00
2019-09-20 04:27:57 -05:00
## Overview
2019-07-03 02:50:42 -05:00
Docs: Add links, fix grammar, formatting, wording (#22381)
* Docs: Add links, fix grammar, formatting, wording
- Add links to theme files and technology references
- Adjust formatting to be consistent, e.g., syntax highlighting, section spacing
- Fix misc grammar, punctuation
- Fix SASS -> Sass
Co-Authored-By: Arve Knudsen <arve.knudsen@gmail.com>
Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
2020-02-24 16:05:56 -06:00
**Themes are implemented in Typescript.** That's because our goal is to share variables between Grafana TypeScript and [Sass ](https://sass-lang.com/ ) code. Theme definitions are located in the following files:
- [packages/grafana-ui/src/themes/dark.ts ](../../packages/grafana-ui/src/themes/dark.ts )
- [packages/grafana-ui/src/themes/default.ts ](../../packages/grafana-ui/src/themes/default.ts )
- [packages/grafana-ui/src/themes/light.ts ](../../packages/grafana-ui/src/themes/light.ts )
The `default.ts` file holds common variables like typography and spacing definitions, while `[light|dark].ts` primarily specify colors used in themes.
2019-07-03 02:50:42 -05:00
2019-09-20 04:27:57 -05:00
## Usage
Docs: Add links, fix grammar, formatting, wording (#22381)
* Docs: Add links, fix grammar, formatting, wording
- Add links to theme files and technology references
- Adjust formatting to be consistent, e.g., syntax highlighting, section spacing
- Fix misc grammar, punctuation
- Fix SASS -> Sass
Co-Authored-By: Arve Knudsen <arve.knudsen@gmail.com>
Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
2020-02-24 16:05:56 -06:00
This section provides usage guidelines.
2019-09-20 04:27:57 -05:00
### Using themes in React components
2019-07-03 02:50:42 -05:00
Docs: Add links, fix grammar, formatting, wording (#22381)
* Docs: Add links, fix grammar, formatting, wording
- Add links to theme files and technology references
- Adjust formatting to be consistent, e.g., syntax highlighting, section spacing
- Fix misc grammar, punctuation
- Fix SASS -> Sass
Co-Authored-By: Arve Knudsen <arve.knudsen@gmail.com>
Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
2020-02-24 16:05:56 -06:00
Here's how to use Grafana themes in React components.
2020-07-01 04:39:46 -05:00
#### useStyles hook
`useStyles` memoizes the function and provides access to the theme.
2019-07-03 02:50:42 -05:00
2019-09-20 04:27:57 -05:00
```tsx
2020-07-01 04:39:46 -05:00
import React, { FC } from 'react';
import { GrafanaTheme } from '@grafana/data';
import { useStyles } from '@grafana/ui';
import { css } from 'emotion';
2019-07-03 02:50:42 -05:00
2020-07-01 04:39:46 -05:00
const getComponentStyles = (theme: GrafanaTheme) => css`
padding: ${theme.spacing.md};
`;
const Foo: FC< FooProps > = () => {
const styles = useStyles(getComponentsStyles);
// Use styles with className
};
2019-07-03 02:50:42 -05:00
```
2020-07-01 04:39:46 -05:00
#### Get the theme object
2019-07-03 02:50:42 -05:00
2019-09-20 04:27:57 -05:00
```tsx
2020-07-01 04:39:46 -05:00
import React, { FC } from 'react';
import { useTheme } from '@grafana/ui';
2019-07-03 02:50:42 -05:00
2020-07-01 04:39:46 -05:00
const Foo: FC< FooProps > = () => {
const theme = useTheme();
2019-09-09 01:18:38 -05:00
// Your component has access to the theme variables now
2020-07-01 04:39:46 -05:00
};
```
#### Using `ThemeContext` directly
```tsx
import { ThemeContext } from '@grafana/ui';
< ThemeContext.Consumer > {theme => < Foo theme = {theme} / > }< / ThemeContext.Consumer > ;
2019-07-03 02:50:42 -05:00
```
2019-11-21 09:52:57 -06:00
#### Using `withTheme` higher-order component (HOC)
2019-07-03 02:50:42 -05:00
Docs: Add links, fix grammar, formatting, wording (#22381)
* Docs: Add links, fix grammar, formatting, wording
- Add links to theme files and technology references
- Adjust formatting to be consistent, e.g., syntax highlighting, section spacing
- Fix misc grammar, punctuation
- Fix SASS -> Sass
Co-Authored-By: Arve Knudsen <arve.knudsen@gmail.com>
Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
2020-02-24 16:05:56 -06:00
With this method your component will be automatically wrapped in `ThemeContext.Consumer` and provided with current theme via `theme` prop. Components used with `withTheme` must implement the `Themeable` interface.
2019-07-03 02:50:42 -05:00
```ts
import { ThemeContext, Themeable } from '@grafana/ui';
interface FooProps extends Themeable {}
const Foo: React.FunctionComponent< FooProps > = () => ...
export default withTheme(Foo);
2019-11-21 09:52:57 -06:00
```
Docs: Add links, fix grammar, formatting, wording (#22381)
* Docs: Add links, fix grammar, formatting, wording
- Add links to theme files and technology references
- Adjust formatting to be consistent, e.g., syntax highlighting, section spacing
- Fix misc grammar, punctuation
- Fix SASS -> Sass
Co-Authored-By: Arve Knudsen <arve.knudsen@gmail.com>
Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
2020-02-24 16:05:56 -06:00
### Test components that use `ThemeContext`
2019-11-21 09:52:57 -06:00
When implementing snapshot tests for components that use the `withTheme` HOC, the snapshot will contain the entire theme object. Any change to the theme renders the snapshot outdated.
To make your snapshot theme independent, use the `mockThemeContext` helper function:
```tsx
import { mockThemeContext } from '@grafana/ui';
import { MyComponent } from './MyComponent';
describe('MyComponent', () => {
let restoreThemeContext;
beforeAll(() => {
// Create ThemeContext mock before any snapshot test is executed
restoreThemeContext = mockThemeContext({ type: GrafanaThemeType.Dark });
});
afterAll(() => {
// Make sure the theme is restored after snapshot tests are performed
restoreThemeContext();
});
2020-07-01 04:39:46 -05:00
2020-06-30 16:42:50 -05:00
it('renders correctly', () => {
2019-11-21 09:52:57 -06:00
const wrapper = mount(< MyComponent / > )
expect(wrapper).toMatchSnapshot();
});
});
2019-07-03 02:50:42 -05:00
```
2019-09-20 04:27:57 -05:00
## FAQ
Docs: Add links, fix grammar, formatting, wording (#22381)
* Docs: Add links, fix grammar, formatting, wording
- Add links to theme files and technology references
- Adjust formatting to be consistent, e.g., syntax highlighting, section spacing
- Fix misc grammar, punctuation
- Fix SASS -> Sass
Co-Authored-By: Arve Knudsen <arve.knudsen@gmail.com>
Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
2020-02-24 16:05:56 -06:00
This section provides insight into frequently-asked questions.
### How can I modify Sass variable files?
2020-07-01 04:39:46 -05:00
**If possible, migrate styles to Emotion**
2019-09-20 04:27:57 -05:00
> For the following to apply you need to run `yarn dev` task.
Docs: Add links, fix grammar, formatting, wording (#22381)
* Docs: Add links, fix grammar, formatting, wording
- Add links to theme files and technology references
- Adjust formatting to be consistent, e.g., syntax highlighting, section spacing
- Fix misc grammar, punctuation
- Fix SASS -> Sass
Co-Authored-By: Arve Knudsen <arve.knudsen@gmail.com>
Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
2020-02-24 16:05:56 -06:00
`[_variables|_variables.dark|_variables.light].generated.scss` files are the ones that are referenced in the main Sass files for Sass variables to be available. **These files are automatically generated and should never be modified by hand!**
2019-09-20 04:27:57 -05:00
2020-07-01 04:39:46 -05:00
#### If you need to modify a _Sass variable value_ you need to modify the corresponding Typescript file that is the source of the variables:
2019-09-20 04:27:57 -05:00
- `_variables.generated.scss` - modify `grafana-ui/src/themes/default.ts`
- `_variables.light.generated.scss` - modify `grafana-ui/src/themes/light.ts`
- `_variables.dark.generated.scss` - modify `grafana-ui/src/themes/dark.ts`
2020-07-01 04:39:46 -05:00
#### If you need to _add new variable_ to Sass variables you need to modify corresponding template file:
2019-09-20 04:27:57 -05:00
- `_variables.generated.scss` - modify `grafana-ui/src/themes/_variables.scss.tmpl.ts`
- `_variables.light.generated.scss` - modify `grafana-ui/src/themes/_variables.light.scss.tmpl.ts`
- `_variables.dark.generated.scss` - modify `grafana-ui/src/themes/_variables.dark.scss.tmpl.ts`
## Limitations
Docs: Add links, fix grammar, formatting, wording (#22381)
* Docs: Add links, fix grammar, formatting, wording
- Add links to theme files and technology references
- Adjust formatting to be consistent, e.g., syntax highlighting, section spacing
- Fix misc grammar, punctuation
- Fix SASS -> Sass
Co-Authored-By: Arve Knudsen <arve.knudsen@gmail.com>
Co-Authored-By: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
2020-02-24 16:05:56 -06:00
This section describes limitations with Grafana's theming system.
### You must ensure `ThemeContext` provider is available in a React tree
By default all react2angular directives have `ThemeContext.Provider` ensured. But, there are cases where we create another React tree via `ReactDOM.render` . This happens in the case of graph legend rendering and the `ReactContainer` directive. In such cases theme consumption will fail. To make sure theme context is available in such cases, you need to wrap your rendered component with ThemeContext.Provider using the `provideTheme` function:
2019-07-03 02:50:42 -05:00
2019-09-20 04:27:57 -05:00
```ts
2019-07-03 02:50:42 -05:00
// graph.ts
import { provideTheme } from 'app/core/utils/ConfigProvider';
// Create component with ThemeContext.Provider first.
// Otherwise React will create new components every time it renders!
const LegendWithThemeProvider = provideTheme(Legend);
const legendReactElem = React.createElement(LegendWithThemeProvider, legendProps);
ReactDOM.render(legendReactElem, this.legendElem, () => this.renderPanel());
```
`provideTheme` makes current theme available via ThemeContext by checking if user has `lightTheme` set in her boot data.