-
Notifications
You must be signed in to change notification settings - Fork 14
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(components-angular): rename package to intranet-header-workspace #2072
Conversation
|
Preview environment ready: https://preview-2072--swisspost-web-frontend.netlify.app |
# Conflicts: # pnpm-lock.yaml
…ent-angular package
# Conflicts: # packages/demo/package.json # packages/intranet-header-workspace/package.json # packages/intranet-header-workspace/projects/intranet-header/package.json # pnpm-lock.yaml
@@ -15,7 +15,7 @@ name: Build Demo App | |||
on: | |||
pull_request: | |||
paths: | |||
- 'packages/components-angular/**' | |||
- 'packages/intranet-header-workspace/**' |
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.
Why add the suffix -workspace
?
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.
Because this package IS actually an angular-workspace: https://angular.io/guide/file-structure.
And the actual package, which is gonna be released, is inside of this workspace: intranet-header-workspace/projects/intranet-header
Co-authored-by: Loïc Fürhoff <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
#2072 introduces some sub-dependencies changes similarly to the initial PR of this revert: #2083. This breaks e2e tests for components and internet-header. `*.entry.js` files are not generated/copied to the documentation assets folder and creates a 404 when we try to use a web component. For testing, I cherry-pick the commit of this PR to #2140 Also upgrading to Stencil 4 (#2116) does not fix this issue.
This is necessary to make room for the up coming
components-angular
package, generated out of thecomponents
package.