-
Notifications
You must be signed in to change notification settings - Fork 366
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
Fully support customize style by classes
options
#714
Comments
We don't need to get context from classer but from Sandpack context. |
Hey, thanks for opening this issue. That is a very interesting point! Could you open a PR to start a discussion around this problem? We could implement our own version of this To be honest, I think we can make something smarter and take advantage of the |
@danilowoz OK, I will start a PR for this. You are right it's better to have a comman pattern to handle all the class name related stuff, I will think about and try to make some design. |
Tell us how you think we can improve Sandpack
Currently there is an option
classes
for people who want to fully customize style for sandpack and remove the default styles generate by stitches. But it seems the feature is not fully supported, by my test there are some problems:sp-file-expoler
/sp-preview
etc.I want to add fully support to the
sp
prefixed classes so we can fully customize sandpack appearance using tailwindcss or other class name based style solution.Packages affected
What is this feature?
Fully support customize sandpack style by
classes
option.How would your idea work?
For components, just add correct
useClasser
class names.For code highlight, we need to get the full classes map and get correct class name at:
The problem is
@code-hike/classer
did not expose thecontext
and any other hooks to get the wholeclasses
map. Besides the package not being updated in last year so I suppose we can maintain the implementation ourself.Do you have any examples of how you would like to see us implement it?
No currently.
I will code to PR if you do not have any other concern.
The text was updated successfully, but these errors were encountered: