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
If this is a bug, please explain how to reproduce the problem
Which tools did you use in which sequence?
Is the error concerning a text or a volume annotation?
Which label set has been used for the volume annotation (if applicable)?
What is the type and resolution of your data? (Can you provide a link to your data?)
Do not include sensitive information.
Upload the browser error message if you are familiar with web developer tools.
The route /user/json/:userName/atlas doesn't work since the function getUserAtlasSlice in dataSlices.js is buggy (use of for...in statement like if it were for...in and call to the i variable which is not initialized), so if we call it provided that we have some atlases we get the following json: {"success":false,"list":[]}.
That function is not used anywhere in brainbox except in the unit test 'should return the correct atlas slice with valid input', but since the user foo doesn't have any atlas, the test is happy because it gets an empty list with success=true
Expected behaviour
/user/json/:userName/atlas route should work correctly and the unit test should really test that an atlas slice is returned.
Version information (for bug reports)
current
The text was updated successfully, but these errors were encountered:
Thank you for your feedback.
Is it a [x] bug report or a [ ] feature request?
Current behaviour
The route
/user/json/:userName/atlas
doesn't work since the functiongetUserAtlasSlice
indataSlices.js
is buggy (use offor...in
statement like if it werefor...in
and call to thei
variable which is not initialized), so if we call it provided that we have some atlases we get the following json:{"success":false,"list":[]}
.That function is not used anywhere in brainbox except in the unit test
'should return the correct atlas slice with valid input'
, but since the user foo doesn't have any atlas, the test is happy because it gets an empty list with success=trueExpected behaviour
/user/json/:userName/atlas
route should work correctly and the unit test should really test that an atlas slice is returned.Version information (for bug reports)
current
The text was updated successfully, but these errors were encountered: