Add data fetching capabilities to data providers #251
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.
What it does
Introduce a new interface and model class to allow data providers to fetch and return custom data based on provider configuration.
ITmfDataProviderConfigurationDataFetcherinterface that allows data providers to implement custom data retrieval capabilities without requiring specific knowledge of the data format in the core API.TmfDataProviderConfigurationDataModelclass to encapsulate different types of content (files, byte arrays, strings, etc.) along with associated metadata such as content type and filename.This extension enables data providers to serve various types of content (reports, images, data exports, etc.) in a standardized way while keeping the core API independent of specific implementations.
How to test
Run the project tests via
mvn clean test.Follow-ups
Any data provider configuration that needs to have such a functionality can implement the
ITmfDataProviderConfigurationDataFetcherinterface and provide the required logic in order to retrieve its data.Review checklist