Before the awesome bootdev cli tool, users could see "jwtToken1" variables be replaced with the actual token in the feedback. This was a fairly recent change that all but eliminated reports that the tests were broken. Users see the "jwtToken1" in the request and assume the problem is the test instead of their faulty code.
If the CLI doesn't already, is it maybe worth considering possibly adding this to the bootdev CLI someday?
Example report about "broken tests" because users don't realize their code is wrong:
Before the awesome bootdev cli tool, users could see "jwtToken1" variables be replaced with the actual token in the feedback. This was a fairly recent change that all but eliminated reports that the tests were broken. Users see the "jwtToken1" in the request and assume the problem is the test instead of their faulty code.
If the CLI doesn't already, is it maybe worth considering possibly adding this to the bootdev CLI someday?
Example report about "broken tests" because users don't realize their code is wrong:
https://github.com/bootdotdev/courses/issues/6894
Example CLI response missing interpolation:
Example client response missing interpolation: