-
Notifications
You must be signed in to change notification settings - Fork 556
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
Is there an abbr for improvement
?
#66
Comments
Hey @htchaan thank you for the question! I think it's quite long too, but at the moment there's no abbreviation for Good ideas are always welcome 😄 |
Would |
@pmackay I think Any other suggestion? |
I vote for `impr`. Its 4-char just like many other abbreviations eg.
`elem`, `feat`, `impl`.
Damiano Petrungaro <[email protected]> 於 2018年7月19日週四 上午12:49寫道:
… @pmackay <https://github.com/pmackay> I think improve is more a verb than
a noun.
Any other suggestion?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#66 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACSbWf9sj76KhfntefJU2OWnb5mbImq5ks5uH2cvgaJpZM4VHNnY>
.
|
I didn't realize we recommended
Honestly, if it's a code change, then the only non-feature, non-bug, improvement would be a performance one, and for that you could use the Angular convention of Basically, I'm taking a step back and asking, do we even need improvement? What does it communicate that feat, fix, and perf, do not? |
What would a refactoring for code cleanup fit under? |
The Conventional Commits documentation states: So I personally use |
Hey! @hbetts I suggested some months ago to introduce Instead I am totally open to rediscuss it! edit:
|
I think I've used For example, I will deprecate a function as part of a Then, at a later time, I will remove that function in a I'm sorry if I'm derailing this issue. If y'all would like my thoughts on As for abbreviation, yes, I would be fine with the recommendations. In particular, Any way to quantify the common abbreviated form of |
@hbetts I'm totally fine about talking about it, our mission is to make the specs as better as possible 😄 As you can see I do not agree with the usage of Looking forward to any English native speaker about it
|
I've spun off a discussion about As for this issue, I don't have the time to research whether Does anyone else have time? |
@hbetts I can take a look tomorrow ;) |
👋 any objection to closing this pull request, I think the spec appropriately calls out the fact that folks can pick and choose their own types. |
I think we should close this one and reopen #78 |
Closing now. Feel free to comment. |
wait, so are we using imp: ? |
|
Since
improvement
(11 chars) is even longer thanfeature
(7 chars), which is shortened asfeat
.The text was updated successfully, but these errors were encountered: