You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inside of an existing project, create a malformed package.json.
Run: notion install ember-cli (any notion command will work)
Encounter incorrect error message
Actual result:
error: Could not parse project manifest
at /private/tmp/foobaz/package.json
Please ensure that the file is correctly formatted.
Error details written to: notion-error-2019-04-16_23_00_10.847.log
Expected result:
error: Could not parse project manifest at /private/tmp/foobaz/package.json
Please ensure that the file is correctly formatted.
Error details written to: <FULL_PATH_TO_FILE>/notion-error-2019-04-16_23_00_10.847.log
Encountered this with notion v0.3.0
The text was updated successfully, but these errors were encountered:
For the first issue, the newline is there for reasons of line length and wanting to make sure that arbitrary paths / urls aren't stuck onto the end of a line where they are likely to wrap. If it's more consistent with other tools and users aren't as worried about a path being cut in half because of wrapping, I can see switching it.
For the full path to the error log, I agree. I went back and forth on showing it, for similar stylistic reasons, but I think ultimately the bad UX of going "Okay great, where is that file?" is worse than the potential of a line being wrapped in the middle of a path.
Steps to Reproduce
package.json
.notion install ember-cli
(any notion command will work)Actual result:
Expected result:
Encountered this with notion v0.3.0
The text was updated successfully, but these errors were encountered: