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

feat(unstable): remove --unstable-workspaces flag #21891

Merged
merged 4 commits into from
Jan 14, 2024

Conversation

bartlomieju
Copy link
Member

The flag is kept for existing CLI compatibility, but is not required anymore.

The workspaces feature is still considered unstable and can change. Requiring this flag
hinders DX.

@bartlomieju bartlomieju added this to the 1.40 milestone Jan 10, 2024
@bartlomieju bartlomieju changed the title feat: remove --unstable-workspaces flag feat(unstable): remove --unstable-workspaces flag Jan 10, 2024
Copy link
Member

@dsherret dsherret left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -1032,13 +1031,12 @@ fn clap_root() -> Command {
.global(true),
)
.arg(
// NOTE(bartlomieju): not used anymore, but kept for CLI compatibility between
Copy link
Member

Choose a reason for hiding this comment

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

I think it's not too big of a deal to just remove this? It's unstable and not a lot of people are using it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure I can do that.

@bartlomieju bartlomieju enabled auto-merge (squash) January 14, 2024 21:18
@bartlomieju bartlomieju merged commit a918804 into denoland:main Jan 14, 2024
14 checks passed
@bartlomieju bartlomieju deleted the remove_unstable_workspaces branch January 14, 2024 22:23
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