Closed EricSoroos closed 4 years ago
@EricSoroos we should avoid changing sourceData.scenarios
as the property name for scenario data, as the change would affect the data service. I pushed changes reverting this and altering the behavior of the button dropdown. Now it will only display a download button if it is available in the model description. The later behavior was to show a disabled button when the link was not available.
I suggest updating the model config files to follow the current naming while @danielfdsilva reviews this PR.
If the pr doesn't work when it's unmerged, it doesn't make sense to revert it, just don't merge it and add something that does. My read of the source is that sourcedata is just passed through as an opaque parameter, so as long as it's json we're good.
Properties sourceData.scenarios
and sourceData.clusters
are part of the model validation schema and used in test fixtures.
So the net result of this PR is a lint commit?
Buttons were disabled instead of being hidden when the links were not available.
Make a single link to the dataset hosting all of the source data for a model