-
Notifications
You must be signed in to change notification settings - Fork 32
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
Chore: make a bunch of components standalone #1047
Conversation
|
Affected libs:
|
📷 Screenshots are here! |
419cd22
to
b1557ec
Compare
b1557ec
to
79d4da8
Compare
79d4da8
to
210451d
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.
Pfiou, tedious PR, thanks @jahow ! Took a look over the code, started the datahub, editor and storybook and could only make out some issues on the latter.
Some components like TableView
, ApiCardComponent
, GnUiLinkifyDirective
throw an error like Unexpected "LoadingMaskComponent" found in the "declarations" array of the "StorybookComponentModule" NgModule, "LoadingMaskComponent" is marked as standalone and can't be declared in any NgModule - did you intend to import it instead (by adding it to the "imports" array)?
in storybook.
FigureContainerComponent
and FigureComponent
have issues with the TranslateService
, but not sure if that is related to this PR.
LoadingMaskComponent, | ||
SpinningLoaderComponent, | ||
], | ||
declarations: [ColorScaleComponent, StepBarComponent], |
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.
Just for better understanding. How did you decide, which components to make standalone in each module and which ones to keep as is for now? Did you encounter any architectural limitations?
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.
Good question, my approach was to pull on the thread and see what comes. So I'd start with a component that's not standalone and make it standalone and then see what components are affected and make them standalone in turn, etc. :)
thank you @tkohr , indeed many storybook entries were failing! I went through all of them and fixed them. |
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.
Thanks, working fine now 🤩, just the e2e are red.
Description
The impacted components are:
Quality Assurance Checklist
breaking change
labelbackport <release branch>
label