-
Notifications
You must be signed in to change notification settings - Fork 37
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
Change description key #70
Comments
@DrVanScott: It's named |
@seletskiy: I understand and that's why i wrote "or vice verse". The main point of my argument is the key name. It does not match the key in external-hooks.properties nor does it match the naming scheme. Look at line 27:
Attribute "i18n-name-key" and "key" are aligned (Same for the description key in the next line) A minor side effect of this is: The description for the first (and last) hook is taken from the properties file, while the description of async hook is taken from the xml, due to no match in the property file. Not a big deal, just something against my pedantic mind... ;-) |
@DrVanScott: ah, I see what you mean now. I'm not sure however that it can be changed safely, because Bitbucket may store settings for hooks by it's key and this change may not be backward compatible. |
I agree not to change "key", but it should be possible to change "i18n-name-key". At least make a change in external-hook.properties to make this mechanism also work for the async hook. Whatever solution you choose, you need to change the content of async's description in the property file. |
Just a small issue:
atlassian-external-hooks/src/main/resources/atlassian-plugin.xml
Line 39 in ff92abf
Better change
to
Accordingly change the in place description from
to (external-hooks.properties)
or vice versa?
The text was updated successfully, but these errors were encountered: