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.

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

tools(foreach): replace relative to absolute paths in build output #2109

Merged
merged 1 commit into from
Mar 28, 2019

Conversation

eladb
Copy link
Contributor

@eladb eladb commented Mar 28, 2019

this allows running "foreach" from the IDE and have problems
discovered globally.

this allows running "foreach" from the IDE and have problems
discovered globally.
@eladb eladb requested a review from a team as a code owner March 28, 2019 08:01
@RomainMuller RomainMuller merged commit 7001f77 into master Mar 28, 2019
@RomainMuller RomainMuller deleted the benisrae/foreach-absolute-paths branch March 28, 2019 10:10
@Doug-AWS
Copy link
Contributor

Is this change exposed to the user? If so, is there a use case that we should document in the guide?

@NGL321 NGL321 added the contribution/core This is a PR that came from AWS. label Sep 23, 2019
@mergify
Copy link
Contributor

mergify bot commented Sep 23, 2019

Thanks so much for taking the time to contribute to the AWS CDK ❤️

We will shortly assign someone to review this pull request and help get it
merged. In the meantime, please take a minute to make sure you follow this
checklist
:

  • PR title type(scope): text
    • type: fix, feat, refactor go into CHANGELOG, chore is hidden
    • scope: name of module without aws- or cdk- prefix or postfix (e.g. s3 instead of aws-s3-deployment)
    • text: use all lower-case, do not end with a period, do not include issue refs
  • PR Description
    • Rationale: describe rationale of change and approach taken
    • Issues: indicate issues fixed via: fixes #xxx or closes #xxx
    • Breaking?: last paragraph: BREAKING CHANGE: <describe what changed + link for details>
  • Testing
    • Unit test added. Prefer to add a new test rather than modify existing tests
    • CLI or init templates change? Re-run/add CLI integration tests
  • Documentation
    • README: update module README to describe new features
    • API docs: public APIs must be documented. Copy from official AWS docs when possible
    • Design: for significant features, follow design process

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants