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
I'm not sure why, but it seems that the jasper2 migrator had some bugs in the yaml file that caused issues after it was merged during a rerender.
I think a simple test, that tries to "read" the yaml file, to ensure there are any bugs in the yaml syntax would go a long way.
yaml
I've addressed the immediate issue in ; #1940
The text was updated successfully, but these errors were encountered:
I am so sorry for breaking things with jasper2.yaml. I just now reproduced what I did wrong
jasper2.yaml
vim jasper2.yaml
Sorry, something went wrong.
It seemed that I missed some other non-ascii characters #1943
No branches or pull requests
I'm not sure why, but it seems that the jasper2 migrator had some bugs in the yaml file that caused issues after it was merged during a rerender.
I think a simple test, that tries to "read" the yaml file, to ensure there are any bugs in the
yaml
syntax would go a long way.I've addressed the immediate issue in ;
#1940
The text was updated successfully, but these errors were encountered: