We want to establish smooth communication between the application server and intelligence service using OpenAPI specifications, while minimizing manual processes.
Closes #33
Description
The OpenAPI specification is stored in the intelligence service directory. Based on it a Java client for the application server can be generated (also via root-level package.json script)
Added GitHub Action workflow to fail if the Java client is not up-to-date with the OpenAPI specifications
Checklist
General
[x] PR title is clear and descriptive
[x] PR description explains the purpose and changes
[x] Code follows project coding standards
[x] Self-review of the code has been done
[x] Changes have been tested locally
[ ] Screenshots have been attached (if applicable)
[ ] Documentation has been updated (if applicable)
Client (if applicable)
[ ] UI changes look good on all screen sizes and browsers
[ ] No console errors or warnings
[ ] User experience and accessibility have been tested
[ ] Added Storybook stories for new components
[ ] Components follow design system guidelines (if applicable)
Server (if applicable)
[x] Code is performant and follows best practices
[x] No security vulnerabilities introduced
[ ] Proper error handling has been implemented
[ ] Added tests for new functionality
[ ] Changes have been tested in different environments (if applicable)
Motivation
We want to establish smooth communication between the application server and intelligence service using OpenAPI specifications, while minimizing manual processes. Closes #33
Description
package.jsonscript)Checklist
General
Client (if applicable)
Server (if applicable)