-
Notifications
You must be signed in to change notification settings - Fork 223
Schema build bug #699
New issue
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
Schema build bug #699
Conversation
This is because the Python library dumps JSON with 4-space padding. So if the template has 2-space, if we make even the tiniest change the the diff replaces the whole schema with whitespace changes.
|
Diff without whitespace: https://github.com/nf-core/tools/pull/699/files?diff=unified&w=1 |
This comment has been minimized.
This comment has been minimized.
It did have this previously, but when I switched to using
Odd, that has a space for me: I'll double-space it and add some indentation. |
|
Duplication bug seems to be fixed now. One more bug: the command line keeps waiting for form completion, even after I clicked finished in the browser. |
|
Good spot, fixed in nf-core/website#467 |
|
Now that the website bug has been fixed and merged / deployed, this should work as advertised 👍🏻 |
|
Yes, works as advertised! |
Fix issues with the
schema buildcode that was doing weird stuff when making a new schema - bug found by @mashehuAlso revert the template JSON schema back to 4-space padding instead of 2, to limit the diffs when people edit their schema from the template.