Skip to content

Remove Enso Devtools from built app; show override status even if Devtools is hidden #13330

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

Merged
merged 3 commits into from
Jun 23, 2025

Conversation

somebody1234
Copy link
Contributor

Pull Request Description

  • Remove Enso Devtools from release
  • Show override status even if the Devtools toggle button itself is hidden

Important Notes

None

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.

@somebody1234 somebody1234 added the CI: No changelog needed Do not require a changelog entry for this PR. label Jun 19, 2025
Copy link

github-actions bot commented Jun 19, 2025

✨ GUI Checks Results

Summary

  • 🧹 Prettier: ✅ Passed
  • 🧰 GUI Checks: ✅ Passed
  • 📚 Storybook: ✅ Deployed

All checks passed! Your changes look good to go.

See individual check results for more details.

ℹ️ Chromatic Tests Skipped

Chromatic visual regression tests were skipped for this PR.

To run the tests and deploy Storybook, add the CI: Run Chromatic label to this PR.

Note: We skip tests by default to optimize CI costs. Only run them when your UI changes are ready for review.

👮 Lint GUI Results

Check Results

  • 🧠 Typecheck: ✅ Passed
  • 🧹 Lint: ✅ Passed
  • 🧪 Unit Tests: ✅ Passed

🎭 Playwright Test Results

Summary

  • ⏳ Duration: 7m 58s
  • ✅ Passed: 362 tests
  • 🔴 Failed: 0 tests
  • ⚠️ Flaky: 2 tests

📥 Download Detailed Report

All tests passed! Your changes look good.

Copy link

🔄 GUI Checks in Progress

The following checks are being performed:

  • 🧹 Code formatting with Prettier
  • 👮 Linting and type checking
  • 🧪 Unit tests
  • 🎭 Integration tests with Playwright
  • 📚 Storybook deployment

Results will be updated here once completed.

Copy link
Contributor

Choose a reason for hiding this comment

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

This should not be merged, as no rust code was changed.

Comment on lines 22 to 24
const EnsoDevtools = reactComponent(
process.env.NODE_ENV === 'development' ? EnsoDevToolsReact : () => null,
)
Copy link
Contributor

Choose a reason for hiding this comment

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

This logic is duplicated in EnsoDevTools.tsx. I would either do it only here (and make lazy import maybe?) or only there.

@somebody1234 somebody1234 added the CI: Ready to merge This PR is eligible for automatic merge label Jun 23, 2025
@mergify mergify bot merged commit e81016e into develop Jun 23, 2025
67 of 69 checks passed
@mergify mergify bot deleted the wip/sb/hide-enso-devtools branch June 23, 2025 15:03
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.

2 participants