Skip to content

feat(dbprovider): dataflow support - #6925

Merged
zjy365 merged 16 commits into
labring:mainfrom
aimeritething:dataflow
May 9, 2026
Merged

feat(dbprovider): dataflow support#6925
zjy365 merged 16 commits into
labring:mainfrom
aimeritething:dataflow

Conversation

@aimeritething

Copy link
Copy Markdown
Member

No description provided.

…t, ensuring proper button states based on application status
…nents

- Added new constants for dataflow application key and supported types in `dataflow.ts`.
- Removed `whodb.ts` as its functionality has been integrated into the new dataflow structure.
- Updated `getEnv.ts` to use the new `DATAFLOW_ENABLED` instead of `WHODB_ENABLED`.
- Refactored `Header.tsx` and `dbList.tsx` to utilize the new dataflow constants and adjust logic accordingly.
- Ensured environment store reflects the new dataflow configuration.
…tion changes

- Replaced WHODB_ENABLED and related keys with DATAFLOW_ENABLED in the environment template.
- Ensured the template aligns with recent dataflow feature integration.
@aimeritething
aimeritething requested a review from a team as a code owner April 27, 2026 04:01
@pull-request-size

Copy link
Copy Markdown

Whoa! Easy there, Partner!

This PR is too big. Please break it up into smaller PRs.

@aimeritething aimeritething changed the title Dataflow feat(dbprovider): dataflow support Apr 27, 2026
@zjy365 zjy365 added this to the v5.2 milestone May 9, 2026
aimeritething and others added 2 commits May 9, 2026 17:56
… config

Replace process.env.DATAFLOW_ENABLED / WHODB_ENABLED with a
dataflowForceEnabled field in the YAML config (FeaturesSchema).
Also changes resolveDataflowEnabled() return type from string to boolean.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Eliminate the dataflowForceEnabled field from the YAML config and related code, simplifying the dataflow resolution logic. This change enhances clarity and reduces unnecessary complexity in the configuration and service files.
@zjy365
zjy365 merged commit 91fa34c into labring:main May 9, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants