Fix custom search attributes inputs for different attribute types#3215
Merged
laurakwhit merged 5 commits intomainfrom Mar 10, 2026
Merged
Fix custom search attributes inputs for different attribute types#3215laurakwhit merged 5 commits intomainfrom
laurakwhit merged 5 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
rossedfort
reviewed
Mar 10, 2026
rossedfort
approved these changes
Mar 10, 2026
temporal-cicd bot
pushed a commit
that referenced
this pull request
Mar 10, 2026
Auto-generated version bump from 2.47.2 to 2.47.3 Bump type: patch Changes included: - [`115e9f4f`](115e9f4) always show create schedule button when 0 schedules (#3205) - [`ee254fb1`](ee254fb) Revert Count Schedules API (#3203) - [`954c647e`](954c647) Codefreeze 03.02.26 to main (#3213) - [`93f0e8f4`](93f0e8f) Fix custom search attributes inputs for different attribute types (#3215)
laurakwhit
added a commit
that referenced
this pull request
Mar 10, 2026
Auto-generated version bump from 2.47.2 to 2.47.3 Bump type: patch Changes included: - [`115e9f4f`](115e9f4) always show create schedule button when 0 schedules (#3205) - [`ee254fb1`](ee254fb) Revert Count Schedules API (#3203) - [`954c647e`](954c647) Codefreeze 03.02.26 to main (#3213) - [`93f0e8f4`](93f0e8f) Fix custom search attributes inputs for different attribute types (#3215) Co-authored-by: laurakwhit <15069288+laurakwhit@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description & motivation 💭
Custom search attribute input was not updating based on the attribute type in the "Start a Workflow" form. E.g when selecting a custom search attribute with a
Booltype, the value input stayed as a text input instead of switching to a true/false select.$statevariables (type, value, label) instead of reading directly from attribute (which isn't deeply reactive through$bindable())bind:valueto local state, with an$effectsyncing value back toattribute.valueonly when the local state value changeshandleAttributeChangeupdates local state first, then reassignsattribute = { label, value, type }to notify the parent$derived(attributesToAdd)to$derived([...attributesToAdd])so that when a child updates its attribute via binding, the derived value produces a new array reference, causing all rows to receive updated attributes and re-evaluateisDisabledScreenshots (if applicable) 📸
Design Considerations 🎨
Testing 🧪
How was this tested 👻
Steps for others to test: 🚶🏽♂️🚶🏽♀️
Setup
/workflows/start-workflowpageClick "Add" to add a search attribute row
Boolattribute → verify a true/false select appears and a value can be enteredKeywordattribute → verify a text input appears and a value can be enteredIntattribute → verify a number input appears and a value can be enteredDatetimeattribute → verify a datetime input appears and a value can be enteredKeywordListattribute → verify a chip input appears and a value can be enteredClick the close button on the rows
Select a
KeywordattributeBool→ verify text input is replaced with true/false SelectInt→ verify Select is replaced with number inputKeyword→ verify number input is replaced with text inputAdd a row and select a
BoolattributeBooloption is disabled/greyed outBoolattribute to theKeywordattribute → open the second row's "Search Attribute" select → verify theBoolattribute option is now enabled and theKeywordattribute is disabledChecklists
Draft Checklist
Merge Checklist
Issue(s) closed
DT-3653Docs
Any docs updates needed?