110 bis add an openapi spec inside the project #165
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
differences with branch 110-add-a-openapi-spec-inside-the-project-to-improve-the-documentation-of-the-api-and-verify-devs : - created from more recent main branch - remove get territoire by type - add 2 services for departement
and other fixes
- add DateSuppression for all /geo end-points - add all attributes for /ascendants and /descendants end-points
Swagger parser expect an uri for the location of the openapi.yaml file : so must be modified the inputSpec in the configuration of openapi-generator-maven-plugin
…de-the-project' into 110-bis-add-an-openapi-spec-inside-the-project
generateSupportingFiles->true to allow OpenAPI Generator to generate the utils files, such as ApiUtil Java17 -> Java21
idea:use the tag (departement, commune) but not found how to do => simplified the name in the openapi.yaml file (start with departement, commune)
example : typeOrigine is Departement for end-points /geo/departement/...
example: type=http://rdf.insee.fr/def/geo#Arrondissement at the end of the original request, and has to be transformed into Arrondissement
Seen necessary for geo/departement/{code}/descendants
due to error : Failed to set up a Bean Validation provider: jakarta.validation.NoProviderFoundException: Unable to create a Configuration, because no Jakarta Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath.
issue: No converter for [class java.util.ArrayList] with preset Content-Type 'null'
we want that in any end-point, if the parameter date is null, we replace it by the current date => we do that in ParametersForQuery class (default method). In the contrary, the other parameters stay in descendantsrequestParametier class (class for all end-points with /descendant)
for all end-points, a null attribute must not appear in the response
+ refactor for geo/airesDAttractionDesVilles, geo/arrondissements geo/pays because of some end-points of type geo/"listeTerritoires" have ton contain chefLieu, and other ones not
…sDeleguees geo/intercommunalites
for arrondissementMunicipal Canton CantonOuVille CirconscriptionTerritoriale CommuneAssociee CommuneDeleguee District
…rondissements municipaux
feat: init testcontainers and docker compose
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.