This is the initial version setting up the base system
- 'CNG' Bump quarkus to 1.23.6 and GraalVM to 21.1.0
- 'CNG' Fix typo hierachy -> hierarchy. In fieldnames, methods and comments
- 'NEW' Enable REST data for messages and regions
- 'CNG' Find messages for the region code hierarchy
- 'NEW' Add region type to region and ability to find regions by its type
- 'NEW' REST resources return a paged list, containing page, size, totalElements and totalPages
- 'NEW' Add docker-compose for local and development profile
- 'FIX' Persist updated organization and category fields on existing messages
NEWAdd organization and category field to message- 'CNG' Prefix content type of REST resources with 'vnd.'
CNGChange message geocode relation to optionalCNGRename message tracking topic- 'CNG' Message event type Imported/Created/Updated are processed with create or update
- 'CNG' Raise quarkus version to 1.9.2
NEWAdd single and list message request trackingNEWAdd REST parameter validationsNEWAdd max page size to 50NEWAdd 0.0.0 as unsupported versionNEWAdd region code to message and ability to find messages by region codeNEWAdd region resource to find regions by region code or locationNEWAdd REST method to return a region hierarchy by ars or locationNEWBasic region model- 'CNG' Change to Java 11
NEWAdd Message resource to find a message by its identifierCNGResource path 'api/message' is now 'api/messages'NEWAdd geocode md5 hash to improve findNEWChange Geocode to entityNEWAdd message event type "Disposed" and handlerCNGGeocode field as MultipolygonNEWImplement update and supersede messages service methodsCNGMessage service returns only messages with message type publishedNEWAdd MessageStatus field to message modelNEWRest message request is sorted by publishedAt in descending orderNEWAdd publishedAt field to message modelCNGRenamed message event type: Published -> CreatedNEWMessage service queries point within geocode if presentNEWAdd point (lang & lat) query parameters to REST message requestNEWEnhance message model with geocode fieldNEWAdd Api resource to check if API version is supportedNEWAdd accept header for API versioningNEWMessage rest returns date in ISO 8601 formatNEWSet timezone to UTCNEWAdd Event handler consumes "type: Published"NEWRest resource to request messages (with an optional page request)NEWCreate and read messagesNEWBasic message model
NEWmeans a new featureCNGmeans changed behaviorFIXmeans a bugfix or fix of a glitchREMmeans a removed feature