Closed mootari closed 1 year ago
My best guess is that the path variable {id}
needs to be changed to {seed}
in
as that is what is referenced in
But the variable has remained unchanged since it was originally added, and surely that would have caused the test to fail?
Hi @mootari,
Thank you for reporting this, a fix has been deployed, so this should work correctly now. It seems like it is was indeed broken from the start, and the test was not able to catch it since it doesn't encompass multiple seeds, I'll look into expanding it in the future.
Works beautifully - thank you for the fix and the quick response!
The route
/seed/{seed}/info
always returns the same info. A few examples:In all cases the (formatted) response is: