-
Notifications
You must be signed in to change notification settings - Fork 71
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
User Metadata #2423
User Metadata #2423
Conversation
* Use __user_metadata query if it exists * Update unit tests * Fix tests to not mock response
…e Workflow Header to show summary and details and workflow stats above tabs
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…on, don't refetch workflow-metadata for now. Don't show currentDetails
…l on workflow metadata query, use italics in details
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.
This seems like it shouldn't be a component, accordion is already pretty light, what's the difference?
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.
Less padding, no background, no border, different arrow. Probably more what it will be in the future but didn't want to flip them all over
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.
Let's ask @tigernaut if we can just flip em all over, I'd rather not have 2 versions of accordion
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.
Not gonna on this PR, but ya I'll chat with them on doing that.
class="min-w-fit" | ||
bind:value={name} | ||
data-testid="signal-select" | ||
placeholder="Select a signal" |
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.
i18n
<Option | ||
on:click={handleCustom} | ||
value="custom" | ||
description="Input Signal name">Custom</Option |
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.
i18n
Description & motivation 💭
With the additional of User Metadata and Workflow Metadata, we can show more human-friendly descriptions of workflows and it's current status.
The Summary/Details field is a static field that comes from the WorkflowDescription API.
The Summary/Detailsinfo and the Workflow info (start/end/duration...) will now be above the fold so it will be visible for all tabs.
The Markdown component also will swap out {namespace}, {workflowId} and {runId} strings the the page params to be able to link dynamically.
This also updates the Send Signal modal to use a Select of signal definitions if they exist.
Design Considerations 🎨
Testing 🧪
How was this tested 👻
Steps for others to test: 🚶🏽♂️🚶🏽♀️
Checklists
Draft Checklist
Merge Checklist
Issue(s) closed
Docs
Any docs updates needed?