-
Notifications
You must be signed in to change notification settings - Fork 19
ECHO-615 ECHO-543 Onboarding cards update #394
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
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: Dembrane/echo
Length of output: 1498
🏁 Script executed:
rg -i "default_conversation_tutorial_slug" --type ts --type tsx --type js --type jsx -A 5 -B 2Repository: Dembrane/echo
Length of output: 84
🏁 Script executed:
rg "default_conversation_tutorial_slug" -A 5 -B 2Repository: Dembrane/echo
Length of output: 14171
🏁 Script executed:
rg "None.*basic.*advanced" --type ts -B 5 -A 5Repository: Dembrane/echo
Length of output: 1087
🏁 Script executed:
Repository: Dembrane/echo
Length of output: 89
🏁 Script executed:
Repository: Dembrane/echo
Length of output: 632
🏁 Script executed:
Repository: Dembrane/echo
Length of output: 840
🏁 Script executed:
git log --oneline echo/directus/sync/snapshot/fields/project/default_conversation_tutorial_slug.json | head -10Repository: Dembrane/echo
Length of output: 95
🏁 Script executed:
git log -p --follow -1 echo/directus/sync/snapshot/fields/project/default_conversation_tutorial_slug.json | head -100Repository: Dembrane/echo
Length of output: 39
🏁 Script executed:
grep -A 2 -B 2 '"None"' echo/frontend/src/routes/project/ProjectsHome.tsxRepository: Dembrane/echo
Length of output: 261
Update TypeScript types and new project defaults for consistency; legacy data is safely handled by frontend.
The lowercase choice values (
"skip-consent","none","basic","advanced") anddefault_value: "none"align well with the frontend's slug normalization logic. However, a few inconsistencies need cleanup:ProjectsHome.tsxstill creates new projects with"None"(uppercase), which will be normalized by the frontend'stoLowerCase()validation fallback, but should use"none"directly.typesDirectus.d.tsdefines the type as"None" | "basic" | "advanced"(missing"skip-consent"and using uppercase"None"); update it to match the schema choices."None"(uppercase) will appear as unlisted choices in Directus UI, though the frontend safely defaults them to"none". If you want a clean admin experience, backfill"None"→"none"in the database.🤖 Prompt for AI Agents