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

Dashboard Issues #11685

Merged
merged 13 commits into from
Nov 27, 2024
Merged

Dashboard Issues #11685

merged 13 commits into from
Nov 27, 2024

Conversation

MrFlashAccount
Copy link
Contributor

Pull Request Description

Closes: https://github.com/enso-org/cloud-v2/issues/1592

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.

@MrFlashAccount MrFlashAccount self-assigned this Nov 27, 2024
@MrFlashAccount MrFlashAccount added the CI: No changelog needed Do not require a changelog entry for this PR. label Nov 27, 2024
const currentPlatform = platform()

document.documentElement.setAttribute('data-version', '%ENSO_IDE_VERSION%')
document.documentElement.classList.add(currentPlatform.toLowerCase())
Copy link
Contributor

Choose a reason for hiding this comment

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

scuff

can we prefix the platform name please? so like platform-macos

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Why?

Copy link
Contributor

Choose a reason for hiding this comment

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

i guess mostly to indicate that they are variants of a single property (meaning that there shouldn't be more than one of platform- on any element)

Copy link
Contributor Author

@MrFlashAccount MrFlashAccount Nov 27, 2024

Choose a reason for hiding this comment

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

Not sure what you mean. I can specify macos:text-12 windows:text-24 linux:text-10. Yes, they exclude each other, but i don't understand how platform relates to it

Copy link
Contributor

Choose a reason for hiding this comment

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

oh true 💀 this is a modifier/variant, not a property

but i think regardless it still makes sense to prefix the classes/variants just to make it clear that they are related to each other. just my two cents

also any prefix works, it doesn't have to be platform

@@ -657,6 +657,10 @@ inset 0 -36px 51px -51px #00000014`,

addVariant('not-focus', '&:where([data-rac]):not([data-focused])')
addVariant('not-selected', '&:where([data-rac]):not([data-selected])')

addVariant('windows', '.windows &')
addVariant('macos', '.macos &')
Copy link
Contributor

Choose a reason for hiding this comment

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

if applying the prefix suggestion above then we should do it here too:

      addVariant('platform-macos', 'html.platform-macos &')

Copy link

github-actions bot commented Nov 27, 2024

🧪 Storybook is successfully deployed!

📊 Dashboard:

Copy link
Contributor

@somebody1234 somebody1234 left a comment

Choose a reason for hiding this comment

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

CR ✅

@PabloBuchu PabloBuchu added the CI: Ready to merge This PR is eligible for automatic merge label Nov 27, 2024
@mergify mergify bot merged commit 88ba6fa into develop Nov 27, 2024
50 of 52 checks passed
@mergify mergify bot deleted the wip/sergeigarin/dashboard-issues-1592 branch November 27, 2024 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: No changelog needed Do not require a changelog entry for this PR. CI: Ready to merge This PR is eligible for automatic merge g-dashboard
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants