Make pipeline/frontend/yaml/* types able to be marshaled back to YAML#1835
Conversation
|
was ready just *mostly ... not all types where covered jet :D |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1835 +/- ##
==========================================
- Coverage 21.24% 21.20% -0.04%
==========================================
Files 423 425 +2
Lines 38283 38349 +66
==========================================
Hits 8133 8133
- Misses 29396 29461 +65
- Partials 754 755 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
... so we could in the long run let woodpecker do configuration migrations by itself ... |
|
... this also makes sure we can have more coverage about parsing configs (even if codecouverage is not happy because new code was added :D) ... |
qwerty287
left a comment
There was a problem hiding this comment.
Seems fine so far, I didn't test
|
I agre that the TrueBool is not nice and inexplizit ... after this pull i'll migrate to OptionalBool type witch let us allow to do the same but explizite |
make it able to have pipeline/frontend/yaml/types to be used outside of this repo for serialization etc ...
also allow us to normalize pipeline config by parsing it and re-encoding it ...
... so we could in the long run let woodpecker do configuration migrations by itself ...