You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to reduce some complexity for entry level users of DeepLynx
Upon creating a container, the user should also be provisioned a default, enabled data source.
Further, each new user in the container should start with this default same data source.
Design
It's possible that this feature is more appropriate at a later date, for example after we ramp up work on DeepLynx NextJS. I have laid some groundwork for better state management - e.g. persisting data source selection throughout the app - in DeepLynx NextJS
Medium priority based on what Peter + NRIC may decide, otherwise low priority
Impact
I think we can just add an API call behind the scenes to the container creation workflow
The text was updated successfully, but these errors were encountered:
Reason
We need to reduce some complexity for entry level users of DeepLynx
Upon creating a container, the user should also be provisioned a default, enabled data source.
Further, each new user in the container should start with this default same data source.
Design
It's possible that this feature is more appropriate at a later date, for example after we ramp up work on DeepLynx NextJS. I have laid some groundwork for better state management - e.g. persisting data source selection throughout the app - in DeepLynx NextJS
Medium priority based on what Peter + NRIC may decide, otherwise low priority
Impact
I think we can just add an API call behind the scenes to the container creation workflow
The text was updated successfully, but these errors were encountered: