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(@schematics/angular): don't error out on blank JSON files during migrations #18015

Merged
merged 1 commit into from Jun 26, 2020
Merged

fix(@schematics/angular): don't error out on blank JSON files during migrations #18015

merged 1 commit into from Jun 26, 2020

Conversation

alan-agius4
Copy link
Collaborator

@alan-agius4 alan-agius4 commented Jun 25, 2020

During the solution-style-tsconfig migration we are unexpectedly erroring out when encounter a blank JSON file. This PR fixes this behaviour and also prints the file path when an error occurs when parsing JSON contents.

Closes: #18012 and closes: #18038

@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Jun 25, 2020
@alan-agius4 alan-agius4 requested a review from clydin June 25, 2020 08:58
…migrations

During the solution-style-tsconfig migration we are unexpectedly erroring out when encounter a blank JSON file. This PR fixes this behaviour and also prints the file path when an error occurs when parsing JSON contents.

Closes: #18012
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Jun 25, 2020
@filipesilva filipesilva merged commit 96111ad into angular:master Jun 26, 2020
@alan-agius4 alan-agius4 deleted the empty-json-file branch June 26, 2020 10:35
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade to ng10 issue: invalid JSON character: \n Error while upgrading to v10
4 participants