Adding Bridge pattern to data ingestion #108
Open
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.
The bridge pattern is used to separate the interface of a class from it’s implementation. Then we can have multiple implementations, one to ingest .csv files, one to ingest .dtb files, … etc, and we won't have to worry about it breaking since bridge allows for implementation to be switched at runtime. Then there can be many implementations for many file formats. Then with the bridges adapter, we know the output will work with the rest of Covidify.
By adding the bridge pattern to Covidify I have made it more universal as many more file types may easily be ingested.