-
Notifications
You must be signed in to change notification settings - Fork 0
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
make settings component ready for sdk2
ProjectSettings
type
#117
Comments
@nils.jacobsen can we delete the old settings component and rename settings component 2 to settings component? |
The settings-component is used in production. We might remove it when all apps work on sdk2. |
@nils.jacobsen you can delete the package on the |
actually you have to delete settings-component1 on the lix integration branch. else, we can't publish the component as v2 on npm |
Jap I can do that. |
Context
Whats the status of the settings component and is it already fully transitioned to sdk2 ?
Proposal
Clarify how to use those 2 components, I guess its rather straightforward "use settings-component2" for sdk2 but curious if there is more involved than just that.
The text was updated successfully, but these errors were encountered: