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
Scrambles for 333mbf now contain:
333mbf
"extraScrambles": ["", "", ""]
… where previously they used to contain:
"extraScrambles": []
There are no passcodes for these extras in the passcodes file.
The scrambles are either provides with passcodes, or not at all.
No multiBLD number for round
.json
.zip
This tripped me up while updating https://github.com/cubing/scramble-table/ . Not only did the passcodes file format change a bit, but the JSON is now inconsistent with it.
The text was updated successfully, but these errors were encountered:
Ignore blank extra scrambles for Multi-Blind
760b275
This is a workaround for thewca/tnoodle#895
Note that I don't really need a fix for this, as I've already added a workaround for it.
Sorry, something went wrong.
Thanks, this is indeed not intended.
What do you mean by "Not only did the passcode file format change a bit"?
TNoodle 1.1.2 left off "Scramble Set A" from round descriptions of the passcode files if there was only one scramble set in the round:
cubing/scramble-table@760b275
No branches or pull requests
Actual (problem) behavior
Scrambles for
333mbf
now contain:… where previously they used to contain:
There are no passcodes for these extras in the passcodes file.
Expected behavior
The scrambles are either provides with passcodes, or not at all.
Steps To Reproduce
No multiBLD number for round
#894 until "Generate" works and inspect.json
in the the resulting.zip
.Desktop (please complete the following information):
Additional context [OPTIONAL]
This tripped me up while updating https://github.com/cubing/scramble-table/ . Not only did the passcodes file format change a bit, but the JSON is now inconsistent with it.
The text was updated successfully, but these errors were encountered: