Skip to content

Commit

Permalink
correct file path
Browse files Browse the repository at this point in the history
  • Loading branch information
M-Kusumgar committed Jul 29, 2024
1 parent 1d608e3 commit 0f3f301
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions metadata-structure/metadata-structure.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,9 +27,9 @@ The aim is to unify these differences into one framework that can support all th
The structure we settled on is the backend (this repository) sending the frontend json reponse that tells it how to construct the UI and also how to dynamically update it based on the value of the dropdowns.

Note: For each tab there is a different response that specifies the metadata:
* [`Review output`](inst/schema/CalibrateMetadataResponse.schema.json)
* [`Calibrate model`](inst/schema/CalibratePlotMetadata.schema.json)
* [`Review inputs`](inst/schema/ReviewInputFilterMetadataResponse.schema.json)
* [`Review output`](../inst/schema/CalibrateMetadataResponse.schema.json)
* [`Calibrate model`](../inst/schema/CalibratePlotMetadata.schema.json)
* [`Review inputs`](../inst/schema/ReviewInputFilterMetadataResponse.schema.json)

The structure of these are the same bar the keys to the `plotSettingsControl` which identifies the plot. In the bullet points above there are two main types of dropdowns that we want:
1. Dropdowns that influence other dropdowns - we will call these `controls` and call their values `settings`
Expand Down

0 comments on commit 0f3f301

Please sign in to comment.