Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Tailwind CSS is a much better fit for this project than Emotion CSS. It's easier to code review, easier to refactor and split components, results in smaller CSS bundles, is more accepted by the community, and is collated with the components themselves rather than separate files.
I've configured the Tailwind theme to have the same values as the original Graph Explorer theme, so visually, nothing has changed. Once everything is converted over we can consider changing the theme values back to more Tailwind defaults.
To start off the transition, I converted the Workspace components and ModuleContainer components. These are root level components for the general Graph Explorer layout. This works as a great test case to make sure Tailwind has what we need for the conversion and the theme is configured properly.
I made a few small style changes that improve the layout a bit.
ModuleContainerHeader
ModuleContainerHeader
so controls won't visually "hit the edge"Validation
Related Issues
Check List
license.
pnpm checks
to ensure code compiles and meets standards.pnpm test
to check if all tests are passing.Changelog.md
.