Global YAML: Why does global setting overrride project setting?
Hi there,
I read yesterday that the long-awaited Global Yaml feature is implemented. Well done!
I have a question regarding the implementation. The documentation says that "global config overrides the value defined on project level" in many instances.
I am wondering why you have implemented it like this and not the other way around? Typically, one wants to override global stuff on a per-project if required. This will not be possible anymore and might make migration to global difficult? I feel that it would be better from an API point of view to have a project setting override the global one. Can you give me your thoughts on this?
Take care,
Michael
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 05 May, 2020 04:13 PM
Hi Michael,
It's, actually, project configuration overrides global configuration, or more precisely global configuration sections override and being injected into project ones. What part of docs have confused you? We might to improve it. Also, do you have an example of what would you like to solve with global config?
2 Posted by michael on 06 May, 2020 03:36 PM
HI Feodor
Ok I am super confused here. The documentation says
"global config overrides the value defined on project level"
I will have to think about an example where this particular behavior would be required. We will make use of the global config very soon and I will report back
Maybe the wording in the documentation should be changed ?
e.g.
"global config overrides the value defined on project level" change to
"global config DOSE NOT override the value defined on project level"
?
Support Staff 3 Posted by Feodor Fitsner on 06 May, 2020 04:51 PM
We've re-phrased it to be more clear: https://www.appveyor.com/docs/global-yml/
Obviously, string values defined on project level override the ones defined in global config. There was a mistake. Action lists are merged. Booleans are the only exception, for now - if set to
truein global config it will be alwaystrue. But there are only few of them, so we'll see how it's being accepted.Feodor Fitsner closed this discussion on 06 Jul, 2020 09:03 PM.