We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is related to #3... or builds on it.
The current display of the error messages when Echidna can be a bit cryptic (specially when shown as json).
Specberus Errors: Retrieved "previous" and "latest" documents, but their contents don't match. { name: 'headers.dl', section: 'front-matter', rule: 'docIDFormat' }
It would be nice to show the { ... } stuff in a more human friendly manner, and provide links to, for instance, "docIDFormat".
{ ... }
Also, we might want to replace the word "Specberus" for something more meaningful.
The text was updated successfully, but these errors were encountered:
Relevant code if someone wants to take this on:
spec-prod/src/deploy-w3c-echidna.ts
Lines 177 to 189 in 453bce4
To mimic a run:
"15a512ae-12d6-4031-ae69-1f2a075a1f9c"
publish
INPUTS_DEPLOY=true OUTPUTS_BUILD='{}' node src/deploy-w3c-echidna.js
yarn dev
Sorry, something went wrong.
No branches or pull requests
This is related to #3... or builds on it.
The current display of the error messages when Echidna can be a bit cryptic (specially when shown as json).
It would be nice to show the
{ ... }
stuff in a more human friendly manner, and provide links to, for instance, "docIDFormat".Also, we might want to replace the word "Specberus" for something more meaningful.
The text was updated successfully, but these errors were encountered: