Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Identify unresolved references in L1s #292

Closed
eladb opened this issue Jul 10, 2018 · 2 comments
Closed

Identify unresolved references in L1s #292

eladb opened this issue Jul 10, 2018 · 2 comments
Labels
feature-request A feature should be added or improved.

Comments

@eladb
Copy link
Contributor

eladb commented Jul 10, 2018

During synthesis we should automatically identify unresolved references. This might be something we want to do when we implement cross stack references (see #233)
@eladb
Copy link
Contributor Author

eladb commented Jul 12, 2018

Also related to #330

@eladb eladb added enhancement @aws-cdk/core Related to core CDK functionality labels Dec 17, 2018
@eladb
Copy link
Contributor Author

eladb commented Dec 17, 2018

Related: #1324

@srchase srchase added feature-request A feature should be added or improved. and removed enhancement labels Jan 3, 2019
@eladb eladb changed the title Identify unresolved references Identify unresolved references in L1s Mar 4, 2019
@eladb eladb removed the @aws-cdk/core Related to core CDK functionality label Mar 4, 2019
@eladb eladb closed this as completed Aug 27, 2019
@snyk-bot snyk-bot mentioned this issue Dec 26, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request A feature should be added or improved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@eladb @srchase