EES-4856 Add csv preview, variables, and footnotes to GetDataSetFile #4865
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.
This PR includes additional data in the response returned by
DataSetFileService#GetDataSetFile
:To have these changes work with integration tests,
Testcontainers.Azurite
has been added as a dependency to theContent.Api.Tests
project. This is used to locally spins up a docker container which are then used by integration tests.The
appsettings.IntegrationTest.json
file has also been added to theContent.Api.Tests
project. This was done to ensure that if someone is running the integration tests while they have the data-storage docker container running in the background, the tests don't pass due to reliance on the data-storage container.I've tested the fetching of the first five rows of the data set CSV locally to ensure it's performance is acceptable, and it seemed fine. I've held off doing more exhaustive testing as it'll be easy for us to test this once it's deployed on Prod by visiting the currently hidden Data set details pages - and that'll be testing against current Prod data which seems superior anyway.
I've also moved
DataSetFileMetaViewModel
intoDatSetFileFileViewModel
, since the meta is related to a specific data set file, unlike footnotes, for example, that are linked to a specific data set file/release version combo.