-
-
Notifications
You must be signed in to change notification settings - Fork 590
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
[plugin-replace] Document the values
option
#814
[plugin-replace] Document the values
option
#814
Conversation
packages/replace/README.md
Outdated
Type: `{ [key: String]: Replacement }`, where `Replacement` is either a string or a `function` that returns a string. | ||
Default: `{}` | ||
|
||
To avoid mixing replacement strings with the other options, you can specify replacements in the `values` option: |
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.
To avoid mixing replacement strings with the other options, you can specify replacements in the `values` option: | |
To avoid mixing replacement strings with the other options, you can specify replacements in the `values` option. For example, the following signature: |
packages/replace/README.md
Outdated
|
||
// ⬇ ⬇ ⬇ ⬇ ⬇ ⬇ ⬇ ⬇ ⬇ | ||
|
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.
// ⬇ ⬇ ⬇ ⬇ ⬇ ⬇ ⬇ ⬇ ⬇ | |
Can be replaced with: |
I'm not sure how to suggest code fence / backticks on here, but please separate the two signatures in their own code blocks
Thanks for the PR, a few comments to address but looks solid. |
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.
Updated! Sorry it took three commits, I was trying to do it through the GH ui 😅 |
Rollup Plugin Name:
replace
This PR contains:
Are tests included?
Breaking Changes?
If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers:
Description
I discovered this option because it was used in the
preventAssignment
example, but it wasn't documented.I got the option type from the
.d.ts
file.