Skip to content
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

chore: introduce style package #1

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

chore: introduce style package #1

wants to merge 1 commit into from

Conversation

suddjian
Copy link

💔 Breaking Changes

🏆 Enhancements

📜 Documentation

🐛 Bug Fix

🏠 Internal

@@ -0,0 +1,11 @@
# `style`

> TODO: description
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> TODO: description
> Provides a style object containing a variety of style parameters for theming Superset components with Emotion. See [SIP-37](https://github.com/apache/incubator-superset/issues/9123) for additional context. This will eventually allow for custom themes to override default Superset styles. These parameters (and the styled-components/emotion design pattern) will, over time, be used to whittle away at widely-scoped LESS styles, making it easier to build and (re)style Superset components.

const style = require('..');

describe('style', () => {
it('needs tests');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm... not sure what tests to add here... checking for the existence of styles (in case of accidental deletion) seems a little arbitrary. Really it seems like the components themselves should test for styles. Any thoughts on what's applicable here?

```
const style = require('style');

// TODO: DEMONSTRATE API
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can put together a little sample code for this if you want. Could poach an example from Tai's PR (using the package import, of course) , and add a link to the Emotion docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants