Refactor layer type registration using LayerTypePresets to centralize and streamline configuration management.
#457
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.
Pull Request Overview
This PR refactors layer type registration by introducing a
LayerTypePresetsinterface and ServiceLoader-based discovery mechanism to centralize and streamline configuration management. The hardcoded layer type registrations inSpatialDatabaseServiceare extracted into separate preset classes that can be discovered and loaded dynamically.LayerTypePresetsinterface withRegisteredLayerTyperecord to define layer type configurationsSpatialLayerTypePresets(general types) andOsmSpatialLayerTypePresets(OSM-specific)