-
Notifications
You must be signed in to change notification settings - Fork 19
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: CSS vars updater package #801
base: main
Are you sure you want to change the base?
Conversation
2ffb4eb
to
ac04c82
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Absolutely awesome work on this 🚀 🚀 🚀
I'm still working on the full review, but I did have a couple thoughts about the packaging of the shared helpers that I think are worth bringing up now:
"packages/class-name-updater" | ||
"packages/class-name-updater", | ||
"packages/css-vars-updater", | ||
"packages/shared-helpers" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want lerna managing and releasing the shared-helpers package? Or can it just be a private package that doesn't get published?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was meant to be a private package. It was necessary to add it to this packages list, so lerna can link the packages when building. I updated the shared-helpers
package to be "private": true
.
But if you see a reason to publish it, we can
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah nope, sounds good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh actually..... if it's a full dep in the other packages rather than a devDep will it actually work without the package being published? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point, I don't know. LLM thinks it won't work, which makes sense given that shared-helpers won't be published anywhere. I at first thought that lerna can somehow bundle it into the other packages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like there are ways we could bundle it in, or maybe make it into a devDep, though just publishing it would probably be the fastest/easiest route.
@@ -0,0 +1,22 @@ | |||
{ | |||
"name": "shared-helpers", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it is going to be a public package that we ship I think we should place it under the @patternfly
npm org, and probably give it a more descriptive name like shared-codemod-helpers
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this is valid given your comment above
Closes: #795
class-name-updater
andcss-vars-updater
to ashared-helpers
local packageRelated to the actual css-vars-updater:
npx tsx [path to cli.ts] [path to the test.css file]