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

fix(misc): set schema when converting a project to standalone configuration #13887


Copy link

Current Behavior

When converting a project to a standalone project the $schema property is not set in the generated project.json file. This is not in line with newly generated standalone projects whIch do have the property set.

Expected Behavior

The $schema property should be set in the converted standalone projects' project.json file.

Related Issue(s)

Fixes #

@leosvelperez leosvelperez self-assigned this Dec 17, 2022
Copy link

vercel bot commented Dec 17, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
nx-dev Ready (Inspect) Visit Preview Dec 17, 2022 at 0:22AM (UTC)

@FrozenPandaz FrozenPandaz merged commit a049d6c into nrwl:master Dec 19, 2022
13 checks passed
FrozenPandaz pushed a commit that referenced this pull request Dec 19, 2022
@leosvelperez leosvelperez deleted the misc/set-schema-converted-standalone-project branch December 20, 2022 11:53
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

3 participants