msggen: propagate added and deprecated fields#8873
msggen: propagate added and deprecated fields#8873daywalker90 wants to merge 3 commits intoElementsProject:masterfrom
added and deprecated fields#8873Conversation
f64b2f2 to
3c712b5
Compare
3c712b5 to
33af461
Compare
33af461 to
ae5ed9a
Compare
|
OK, firstly, the explanation here belongs in the commit messages! GitHub is transient (and PRs more so!). Secondly, the second commit is a bad idea: all our documentation should not say each field is added, when it's the entire command which was added. I'm not sure why msggen doesn't just inherit deprecated and added, unless overridden, but msggen is so complex I can never figure out what it's doing already. I've asked Christian how far back he needs msggen to support though! |
ae5ed9a to
1ae8312
Compare
Done, transient as in one 9 of uptime btw 😄
Yeah, what was i thinking. Fixed by inheriting both
Whoops, made it more complex.
Great, otherwise drop the commit. |
1ae8312 to
c4b7bce
Compare
|
I have included a commit to cleanup v26.03 versions with v26.04 versions |
|
The |
added and deprecated fields
Whenever we want to add a new rpc command or notification in msggen's `util.py` we get an error during `make` that the `added` field of that new command or notification is missing even when it's clearly not. We had to uncomment 2 lines in `patch.py` and override any missing `added` annotation to get it running. We now pass any `added` or `deprecated` fields from the parent object correctly so we no longer have to do this. Unfortunately we have commited wrong metadata to `.msggen.json` in the past. This commit also includes missing `added` annotation for commands added after the `pre-v0.10.1` cutoff and manual fixes of the metadata in `.msggen.json`
Allowing deprecated API's should actually allow them in test_sql_deprecated
c4b7bce to
a802db6
Compare
I think it was and allowing deprecated API's should allow them in |
Whenever we want to add a new rpc command or notification we get an error during
makethat theaddedfield of that new command or notification is missing even when it's clearly not and we had to uncomment those 2 lines inpatch.pyto get it running. The first commit passes anyaddedordeprecatedfields from the root object correctly now so we no longer have to do this.Unfortunately we have commited wrong metadata to
.msggen.jsonin the past, which now came to light sincemsggennoticed someaddedfield mismatches. In the second commit i've used msggen to overrite the wrong metadata in.msggen.json. This of course results in a few changes to the generated code.This leads me to commit 3. Because there were some changes i thought we could use the opportunity to raise the minimum supported version from
v0.10.1to something more realistic likev24.11(age ofxpay)?Changelog-None
Edit: PR changed a bit see later comments.