This repository was archived by the owner on Jan 14, 2025. It is now read-only.
Handle null names field when parsing source map files #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
If
names
doesn't exist in a source map file, parsing it fails with the following exception:Source maps created by Dart tooling don't seem to omit this field. However, you will encounter this exception if you use this library to parse a source map that was created by tooling that omits the
names
field when the list is empty. For example, the Go package used by gopherjs to generate source maps omits fields when they are empty. We could update that package so it doesn't omit empty fields when encoding them to json, but it's certainly possible this could be an issue with source maps generated by other toolchains as well.Solution:
Added a null-aware operator to treat a missing
names
field as an empty list.