Fix an issue where messages without text property are shown as undefined [plugin-name]
#46
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.
According to the postcss API document, required properties of
Message
are onlytype
andplugin
.postcss-import
, for example, pushes messages withouttext
property.postcss-reporter
, however, assumes each message hastext
, causingundefined
to be shown as a message body for such messages.Due to this issue, when
postcss-import
andpostcss-calc
are used in this order, the same number ofundefined
messages as that of@import
rules existing in CSS files to be concatinated appear in a console, which is quite annoying. You can get code to reproduce this issue at https://github.com/nodaguti/postcss-calc-warning.This PR fixes the issue by filtering out messages that don't have
text
property in the formatter.