-
Notifications
You must be signed in to change notification settings - Fork 327
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
Remove "X Components" label when editing existing component #12535
Conversation
🧪 Storybook is successfully deployed!📊 Dashboard:
|
<span class="selfArgInfo">{{ selfTypeName ?? 'Input' }} Components</span> | ||
<SvgIcon class="selfArgInfoArrow" name="folder_closed" /> | ||
<span v-if="mode.mode === 'componentBrowsing'" class="selfArgInfo" | ||
>{{ selfTypeName ?? 'Input' }} Components</span |
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.
I think it's a bit confusing to display Any Components
here--the user may not read Any
as referring to a type, in which case it could seem like we meant All Components
. It would help if we format the component type in monospace.
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.
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.
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.
After all we agreed, that, if type is unknown, we don't display the label at all. In that case, Any
should be never visible.
…/fix-component-editing
Pull Request Description
Fixes #12530
Also fixed the case when the type is not yet available (we display "Any Components" in that case)
Important Notes
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[ ] If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,or the Snowflake database integration, a run of the Extra Tests has been scheduled.