-
Notifications
You must be signed in to change notification settings - Fork 2
Feature/mi 277 migrate aspects and restructure #1573
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
base: main
Are you sure you want to change the base?
Conversation
|
Clearly some problems here. But I have no access to Aikido. 😢 |
|
@ryanrixxh It's not Aikido but the error is about merge conflicts. Can you resolve those? |
…e-aspects-and-restructure
kai-nguyen-aligent
left a comment
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.
Great work, @ryanrixxh 👍🏼
Just few small feedback and I think we are in a much better shape than before. It seems to me that eslint config in this repo is broken but we should address it in a different PR.
| @@ -0,0 +1,13005 @@ | |||
| { | |||
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 do we have this file here?
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 need to add something in here?
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 curious, how come we do not have a project.json file for this package 🤣
Description of the proposed changes
After discussions with @TheOrangePuff and @kai-nguyen-aligent the MS team is migrating the CDK Aspects created for our integrations template into the CDK constructs repo.
To better organise the repository, packages have been split into two subfolders, Aspects and Constructs. So as not to make any major breaking changes to the existing packages, Nx has been configured to continue building and publishing the constructs as seperate packages on npm, whilst the aspects due to their size and to not flood the codebase with Nx related bloat are being exported as the one Nx project / npm package.
The PR seems pretty big, but the main actual additions are in the aspects folder. The rest of the changes are changes to configuration files for Nx to allow the build and publish process to operate as normal.
Surely the pipeline doesnt yell at me for this one and that everything goes smooth 🤞
Notes to PR author
Notes to reviewers
🛈 When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback