Replies: 1 comment
-
|
It was discussed during the meeting (12th Jan 2026): The most practical way for the Dedicated Network API would be to simply merge the Pull Request, start using the INCOMPATIBLE_STATE Error Code and align, when we are moving to commonalities 0.7 latest by Fall 26. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The next version of Communalities version will include a new Error Code INCOMPATIBLE_STATE. API Design Guide Section 3.1 (link), NOTE 2 seem to indicate, that {{SPECIFIC_CODE}} (like INCOMPATIBLE_STATE) are ok to be used within the API specification, when be usable among different APIs. There is no restriction, that such a code is listed in Commonalities.
Thus, is it according to API Guidelines, when using the Error Code INCOMPATIBLE_STATE together with Commonalities 0.6 version?
Beta Was this translation helpful? Give feedback.
All reactions