Skip to content
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

Merged
merged 5 commits into from
Mar 21, 2025

Conversation

farmaazon
Copy link
Contributor

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:

  • The documentation has been updated, if necessary.
  • [ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
  • All code follows the
    Scala,
    Java,
    TypeScript,
    and
    Rust
    style guides. In case you are using a language not listed above, follow the Rust style guide.
  • Unit tests have been written where possible.
  • [ ] 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.
    • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

@farmaazon farmaazon added --bug Type: bug -gui labels Mar 18, 2025
@farmaazon farmaazon self-assigned this Mar 18, 2025
Copy link

github-actions bot commented Mar 18, 2025

🧪 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
Copy link
Contributor

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is how it looks:

image

People may think it's a bit ugly. @AdRiley what do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In case of Any:

image

Copy link
Contributor Author

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.

@farmaazon farmaazon added the CI: Ready to merge This PR is eligible for automatic merge label Mar 20, 2025
@jdunkerley jdunkerley added the CI: No changelog needed Do not require a changelog entry for this PR. label Mar 21, 2025
@mergify mergify bot merged commit e080120 into develop Mar 21, 2025
59 checks passed
@mergify mergify bot deleted the wip/farmaazon/fix-component-editing branch March 21, 2025 14:50
@jdunkerley jdunkerley added this to the 2025-Q1 Release milestone Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--bug Type: bug -gui CI: No changelog needed Do not require a changelog entry for this PR. CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Code Edit on a component is showing "Input Components" >
3 participants