-
-
Notifications
You must be signed in to change notification settings - Fork 73
also allow 'parentheses' and 'percent' #617
base: dev
Are you sure you want to change the base?
Conversation
'parantheses' is spelled incorrectly; also allowing 'percent' is simple enough and can save three characters!
I can add a comment in the changelog, but this seems a little insignificant. Let me know if you think it's warranted. If the old spelling is removed later, that would definitely be worth a comment in the changelog, and possibly a deprecation warning beforehand. |
I haven't looked into the testing in this package, but I could also work on some tests for these changes. |
Thanks @theavey - good catch on I like the shorter We're using the |
... or maybe outside PRs won't trigger CI runs in this repo? I notice #614 also didn't trigger CI. @Marc-Andre-Rivet is that the case? Can we enable that? |
The "percent" was less important to me, but it was the word I intuitively put in before looking up the correct keyword. I understand hesitating to put in synonyms for clarity and to avoid bloat. I retargeted the PR, but that seems to have generated the merge conflict because I started from the master branch. |
They didn't. That's changed now. The next commit should trigger CI. parantheses / parentheses: Yes! Let's definitely fix this and tag the misspelled one for deprecation in percent / percentage: Also hesitant to add synonyms or to rename. Since no one seems to feel strongly about it, would drop it from the PR. Could be tagged alongside the typo for renaming in |
@theavey Took the liberty of merging changes from dev and updating the .gitignore file. The build artifacts will need to be removed from the PR. That said, thanks for sticking with it, this PR has been waiting for too long. 🙇 |
For format specifiers, I had two little issues when trying to create a new table:
'parantheses' is spelled incorrectly;
also allowing 'percent' is simple enough and can save three characters!