You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the reduced open api file is often marked as changed in git when a developer starts a full build. The problem here is the unspecific ordering of the methods /json fields.
This is also problematic on a release build - because it was marked as dirty which does block releases!
Wanted
When no additional REST api is defined, the build must produce always the same reduced open api file, no matter how often or on which machine the build is triggered.
Solution
Sort the content of the open api file before writing to disk at build time.
The text was updated successfully, but these errors were encountered:
Situation
Currently the reduced open api file is often marked as changed in git when a developer starts a full build. The problem here is the unspecific ordering of the methods /json fields.
This is also problematic on a release build - because it was marked as dirty which does block releases!
Wanted
When no additional REST api is defined, the build must produce always the same reduced open api file, no matter how often or on which machine the build is triggered.
Solution
Sort the content of the open api file before writing to disk at build time.
The text was updated successfully, but these errors were encountered: