-
Notifications
You must be signed in to change notification settings - Fork 39
Bloom data explorer #5713
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bloom data explorer #5713
Conversation
* feat: data explorer prototype * fix: react deploy issues * feat: call FastAPI for chartData * feat: feature flag * feat: FastAPI is now called via Bloom endpoint * in progress fixes * feat: fix types, call new endpoint, fix mapTo issue * fix: type * fix: use relative imports * test: add unit tests for data-explorer service * add FAST_API env vars to template * fix: merge issues * feat: dto updates, split out frequency objects * feat: data explorer swagger update * fix: add todo * feat: add new endpoint and other features. (#5607) * feat: add generate insights endpoint, fix generate report endpoint, add ai consent storage * fix: reconcile merge conflicts * fix: reconcile merge conflicts --------- Co-authored-by: Chad Brokaw <[email protected]>
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
❌ Deploy Preview for bloom-data-explorer failed. Why did it fail? →
|
✅ Deploy Preview for bloom-lakeview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-angelopolis ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-flagly ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This PR addresses #(insert-number-here)
Description
Please include a summary of the change and which issue(s) is addressed.
How Can This Be Tested/Reviewed?
Provide instructions so we can review, including any needed configuration, and the test cases that need to be QAd.
Author Checklist:
yarn generate:clientand/or created a migration when requiredReview Process: