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

chore: Rk/suggestions for error codes #3417

Merged
merged 10 commits into from
Jan 22, 2024

Conversation

rkoron007
Copy link
Contributor

@rkoron007 rkoron007 commented Jan 12, 2024

I did a quick surface-level overview of all of the error codes for brevity, tone, and style at Nara's request. Most of these are just small tweaks, but please feel free to push back on anything you don't like! ✨

Checklist

  • I have updated the PR title to match CDKTF's style guide
  • I have run the linter on my code locally
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation if applicable
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works if applicable
  • New and existing unit tests pass locally with my changes

@rkoron007 rkoron007 added the documentation Improvements or additions to documentation label Jan 12, 2024
@rkoron007 rkoron007 self-assigned this Jan 12, 2024
@rkoron007
Copy link
Contributor Author

Hi @hashicorp/cdktf! This is a pretty superficial PR(only dealing with the text in error codes), and I'm unfamiliar with the testing practices for CDKTF. Could someone please help advise me on how to pass these PR tests at some point? 🙏

@rkoron007 rkoron007 marked this pull request as ready for review January 13, 2024 00:55
@rkoron007 rkoron007 requested a review from a team as a code owner January 13, 2024 00:55
@rkoron007 rkoron007 requested review from ansgarm and DanielMSchmidt and removed request for a team January 13, 2024 00:55
@rkoron007 rkoron007 changed the title Rk/suggestions for error codes chore: Rk/suggestions for error codes Jan 13, 2024
Co-authored-by: Ansgar Mertens <ansgar@hashicorp.com>
@DanielMSchmidt DanielMSchmidt merged commit a56f4bf into main Jan 22, 2024
431 checks passed
@DanielMSchmidt DanielMSchmidt deleted the RK/suggestions-for-error-codes branch January 22, 2024 15:11
ansgarm pushed a commit that referenced this pull request Jan 23, 2024
## 0.20.2

### feat

- feat(provider-generator): support renaming provider names in order to
allow using two providers sharing the same name at the same time
[\#3442](#3442)
- feat(provider-generator): Ensure we have unique names for modules
[\#3439](#3439)
- feat(docs): Mention Maven examples in note on project setup page
[\#3437](#3437)

### fix

- fix(docs): Run prettier
[\#3445](#3445)
- fix(lib): support dot-seperated nested accessors
[\#3444](#3444)
- fix(docs): Update CLI docs to refer to Gradle instead of Maven
[\#3434](#3434)
- fix(lib): Print a warning with manual steps to move a module when
UpgradeIds aspect encounters modules
[\#3432](#3432)
- fix(cli): don't prompt for providers during convert
[\#3431](#3431)
- fix(lib): inline zip creation
[\#3428](#3428)

### chore

- chore: Upgrade dependencies for @cdktf/hcl2cdk
[\#3452](#3452)
- chore: Upgrade dependencies for @cdktf/hcl2json
[\#3451](#3451)
- chore: Upgrade dependencies for @cdktf/provider-schema
[\#3450](#3450)
- chore: Upgrade dependencies for @cdktf/commons
[\#3449](#3449)
- chore: add CodeTabs component
[\#3443](#3443)
- chore(docs): update stacks documentation
[\#3440](#3440)
- chore: upgrade registry docs tool
[\#3430](#3430)
- chore: Upgrade dependencies for @cdktf/commons
[\#3424](#3424)
- chore(docs): fix currently-404 link to built-in templates
[\#3418](#3418)
- chore: Rk/suggestions for error codes
[\#3417](#3417)
- chore: fix updating script
[\#3396](#3396)
Copy link
Contributor

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants