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

NEXT theme type improvements #2549

Merged
merged 3 commits into from
Mar 13, 2024
Merged

Conversation

endigo9740
Copy link
Contributor

Linked Issue

#2360

Description

Consolidates the preset and custom theme types into a single Theme type. Removes properties_dark and enhancements from the type. Updates the properties to match the current v3 structure.

Copy link

changeset-bot bot commented Mar 13, 2024

⚠️ No Changeset found

Latest commit: 8c64ef3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Mar 13, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
skeleton-docs ❌ Failed (Inspect) Mar 13, 2024 10:11pm
skeleton-next 🔄 Building (Inspect) Visit Preview Mar 13, 2024 10:11pm
skeleton-themes ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 13, 2024 10:11pm

@endigo9740 endigo9740 requested review from ryceg and Hugos68 March 13, 2024 21:01
@endigo9740
Copy link
Contributor Author

endigo9740 commented Mar 13, 2024

@AdrianGonz97 @ryceg @Hugos68 tagging you for review on this as you guys are our resident Typescript pros. The changes are fairly simple, so hopefully nothing too egregious here!

Just FYI I do expect us to add a few additional properties between now and launch. But I'll do my best to ensure those are addressed evenly between all v3 themes. As well as take care to update the type along the way.

I also have /themes/legacy for our v2 themes. Those are just set aside for the moment while we finalize the v3 theme structure. Then I plan to either port those forward or recreate spiritual successors to take advantage of the additional settings. Long story short, don't stress about the typing or structure of those yet.

Copy link
Member

@AdrianGonz97 AdrianGonz97 left a comment

Choose a reason for hiding this comment

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

Deleted one more thing that wasn't needed anymore, but the rest LGTM

Copy link
Contributor

@ryceg ryceg left a comment

Choose a reason for hiding this comment

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

LGTM!

packages/skeleton/scripts/convert-theme.ts Outdated Show resolved Hide resolved
@@ -1,4 +1,4 @@
import type { PresetTheme } from '../index.js';
// import type { Theme } from '../index.js';

const goldNouveau = {
Copy link
Contributor

Choose a reason for hiding this comment

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

I think an extension of Theme that had lines 6 through 19 would be a good idea, so that the themes are typechecked

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think GitHub is aligning this message in the right place, but if you're referring to the properties_dark and enhancements - those aren't carrying over to v3!

@Hugos68
Copy link
Contributor

Hugos68 commented Mar 14, 2024

Was asleep but looks good 😁

@endigo9740 endigo9740 deleted the chore/next-theme-type-improvements branch March 14, 2024 15:24
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.

4 participants