-
Notifications
You must be signed in to change notification settings - Fork 400
Closed
Description
I am using Pattern Lab Node v5.13.2 on Linux, with Node v14.16.0, using a Custom Edition.
Expected Behavior
For reasons (#1309) I currently have the log level set to show errors only. I accidentally introduced some invalid yaml to a pseudo-pattern, which I'd expect to cause an error to be issued.
Actual Behavior
Nothing is output when the log level's set to error.
patternlab-node/packages/core/src/lib/pseudopattern_hunter.js
Lines 47 to 60 in 6120e00
| try { | |
| variantFileFullPath = path.resolve( | |
| paths.source.patterns, | |
| pseudoPatterns[i] | |
| ); | |
| variantFileData = yaml.safeLoad( | |
| fs.readFileSync(variantFileFullPath, 'utf8') | |
| ); | |
| } catch (err) { | |
| logger.warning( | |
| `There was an error parsing pseudopattern JSON for ${currentPattern.relPath}` | |
| ); | |
| logger.warning(err); | |
| } |
Steps to Reproduce
- Set the log level to
error. - Create a pseudo-pattern, and add the following yaml:
make_error: | one two
- Try to build patternlab.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels