In our current build, our components contain both the logic and render elements for an api endpoint. This makes it very difficult to do any markup changes, only CSS can be customized.
Moving to a React Context build, will allow the component library to focus on the logic and allow the catalog applications to focus on the presentation. This means when the DKAN core team releases new features we can update our components to pass that information via Context and catalog developers can decide how they want to present the data.
Initial APIs to include in context:
- Search API
- Dataset from metastore
- General Metastore endpoint
- Datastore for tables
Data Catalog issue: GetDKAN/data-catalog-app#149
In our current build, our components contain both the logic and render elements for an api endpoint. This makes it very difficult to do any markup changes, only CSS can be customized.
Moving to a React Context build, will allow the component library to focus on the logic and allow the catalog applications to focus on the presentation. This means when the DKAN core team releases new features we can update our components to pass that information via Context and catalog developers can decide how they want to present the data.
Initial APIs to include in context:
Data Catalog issue: GetDKAN/data-catalog-app#149