-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(pkglint): allow dependencies on L1 only modules #21208
Conversation
tools/@aws-cdk/pkglint/lib/rules.ts
Outdated
if (maturity === 'cfn-only') { | ||
return; | ||
} | ||
|
||
// eslint-disable-next-line @typescript-eslint/no-require-imports | ||
const stability = require(`${dep}/package.json`).stability; |
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.
We should ignore stability
.
maturity
== how we feel about the reliability of the package.stability
== the default stability of API elements in this package (i.o.w, setting this is just syntactic sugar over putting@stable
,@experimental
etc in every docstring)
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.
See previous comment
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Today, pkglint prevents any module from depending on any experimental module, regardless of its `maturity`. This PR considers `maturity` such that `cfn-only` modules can be taken as dependencies. While writing tests for this is possible, it would be out-of-scope for this PR. ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Today, pkglint prevents any module from depending on any experimental module, regardless of its
maturity
. This PR considersmaturity
such thatcfn-only
modules can be taken as dependencies. While writing tests for this is possible, it would be out-of-scope for this PR.All Submissions:
Adding new Unconventional Dependencies:
New Features
yarn integ
to deploy the infrastructure and generate the snapshot (i.e.yarn integ
without--dry-run
)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license