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

refactor(playground): upgrade playground to be compatible with biome 2.0 #1722

Merged
merged 1 commit into from
Feb 13, 2025

Conversation

dyc3
Copy link
Contributor

@dyc3 dyc3 commented Feb 2, 2025

Summary

This PR updates the playground so that it's compatible with the changes currently on next in the main Biome repo. It needs to be merged after biomejs/biome#4760. The goal for this PR is to simply make the playground functional for 2.0, not to add new features to support new 2.0 functionality.

To test this, I've been using the following command to build the wasm bin and copy over to this repo's node_modules:

wasm-pack build --dev --out-dir ../../packages/@biomejs/wasm-web --target web --scope biomejs crates/biome_wasm --features experimental-html && cp -v packages/@biomejs/wasm-web/* ../biome-website/node_modules/@biomejs/wasm-web

Copy link

netlify bot commented Feb 2, 2025

Deploy Preview for biomejs ready!

Name Link
🔨 Latest commit 799debf
🔍 Latest deploy log https://app.netlify.com/sites/biomejs/deploys/67ae2edd41f88100087d804d
😎 Deploy Preview https://deploy-preview-1722--biomejs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@dyc3 dyc3 force-pushed the playground-next branch 2 times, most recently from fcd98dd to 2c38520 Compare February 5, 2025 15:05
Comment on lines +274 to +280
const importSorting = {
code: "Moved to Analyzer Fixes tab",
};
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 intentional since this PR is focused primarily on simply retaining existing functionality. Planning to fix in a follow up PR.

@ematipico
Copy link
Member

Arend created a next branch here too

#1517

@dyc3
Copy link
Contributor Author

dyc3 commented Feb 6, 2025

FYI, I attempted to merge main into next on the website repo since I was having some trouble with rebasing this PR. Not entirely sure I did it right.

@dyc3 dyc3 force-pushed the playground-next branch 2 times, most recently from bed605f to 06a2851 Compare February 12, 2025 13:49
@dyc3 dyc3 marked this pull request as ready for review February 12, 2025 13:49
@dyc3
Copy link
Contributor Author

dyc3 commented Feb 12, 2025

The integration tests are expected to fail here until this repo synchronizes with the main repo, since it depends on the new api surface.

Copy link
Member

@ematipico ematipico left a comment

Choose a reason for hiding this comment

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

FYI we removed the all option from the workspace, so we need to modify how adding rules that aren't recommended.

A change I had in mind is to have a dropdown with all rules, and then we can add the selected rules to the enabledRules list:

https://github.com/biomejs/biome/blob/b37c1856f6b6521836564328db31e01125772e3f/crates/biome_service/src/workspace.rs#L667-L669

@dyc3 dyc3 removed the next release label Feb 12, 2025
@dyc3
Copy link
Contributor Author

dyc3 commented Feb 12, 2025

Ah yeah I forgot about that. I'll go ahead and update this PR with a workaround and update #1727 with the UI changes.

@dyc3 dyc3 changed the base branch from main to next February 13, 2025 16:43
@dyc3 dyc3 requested a review from a team as a code owner February 13, 2025 16:43
@dyc3 dyc3 force-pushed the playground-next branch 2 times, most recently from e4f3f24 to 82a99d2 Compare February 13, 2025 17:23
@dyc3 dyc3 merged commit ffc96c0 into next Feb 13, 2025
7 checks passed
@dyc3 dyc3 deleted the playground-next branch February 13, 2025 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants