Rüdiger zu Dohna
Rüdiger zu Dohna
> And how about the variant when a pre-built `ClientModel` is used (which is the default behavior in Quarkus now and @mskacelik is working on doing that for WF too)?...
I think the problem is that the `CustomStringScalar` et.al. are not part of the client API. The dependencies of the modules should prevent this code from building, shouldn't it?
BTW: I didn't want to say that it would not be useful to have this.
I can't give an official answer to this question, but Yasson was built as the Reference Implementation RI for Jakarta JSON Binding JSON-B; i.e. its purpose is to prove that...
I found an issue that seems to have exactly the same cause. It works if Yasson first sees the record class directly with the adapter, _before_ it sees it in...
Okay, I see... but wouldn't it make more sense to implement it once? Have you seen #1690
Thanks for the feedback, and after thinking it through, I come to this reasoning about MP Config: dynamic settings like the ones from config sources generally overwrite the static settings...
You're right, if the code provides dynamical credentials (e.g. a bearer token), then it doesn't make sense to still consider MP Config. I guess, I'll have to rethink this.
But that would also change static headers in the code. It needs more than that.
@robp94 : maybe you could provide a PR?