-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
feat: add generic parameters to Modal interfaces #2644
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@matadaniel is attempting to deploy a commit to the Skeleton Labs Team on Vercel. A member of the Team first needs to authorize it. |
@AdrianGonz97 @ryceg if you guys get a chance you can please review this one. Thank you! |
Yeah this looks solid- I'll give it a spin but it's quite a minimal change, but will allow for much better DX. |
@matadaniel Just checking on the status of this one. I noted it's still in a "draft" state, so I wanted to confirm all work is complete. Make sure to bump to "ready for review" when you hit that status. If @ryceg gives the thumbs up we'll merge right away. Thanks! |
I made it a draft PR since you said it would allow you to review sooner rather than later, and I wanted a review to make sure no one's current types would break. I have also not completed much of the PR template checklist. I did come across a discussion that I am unable to find now that mentioned that the ModalSettings.value type should stay as any rather than string. I will add it to the ModalSettings' generic parameters. |
@matadaniel I've had a chance to do a quick review. Overall things look to be working as expected. No regressions have been found per my tests. You are currently missing a Changeset. If you could please follow the instructions provided in the original post at the top of this thread please. Aside from that, I'd recommend either catching your branch up to I'm going to once again ping @ryceg and @AdrianGonz97 to double check that the most recent type changes are sound. If you guys could please use the GitHub PR approval system to report your response! I'll plan to merge once:
Thanks! |
@matadaniel given this PR is getting a bit long in the tooth I'm going to suggest we finalize things by end of this week. Otherwise I'll just make the assumption this isn't moving forward and close the PR. @Hugos68 I'm going to add you as another reviewer since you have a strong handling of types. To all - If I can get one of the three folks tagged here to help confirm, this will be merged per the conditions listed in my post above. |
Alright, we've reached end of the week with no activity so I'm going to call this abandoned and close this out. Just FYI, we're in the midst of shifting our focus from Skeleton v2 -> v3, so this was the last pending item we had hanging on. This now enables us to move forward. Given I do think there's some valuable change here, I've referenced this PR for consideration when we implement the new overlay system in Skeleton v3 here. So some version of this may come back in the future: |
Description
Improve Modal types
Changsets
Instructions: Changesets automate our changelog. If you modify files in
/packages
, runpnpm changeset
in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should beminor
while chores and bugfixes should bepatch
. Please prefix the changeset message withfeat:
,bugfix:
orchore:
.Checklist
Please read and apply all contribution requirements.
dev
branch (NEVERmaster
)docs/
,feat/
,chore/
,bugfix/
pnpm check
pnpm format
pnpm test