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
{{ message }}
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
Currently when I debug a failing test, I have to copy the code into a playground manually. Instead, we could have the link automatically generated. This could be pretty simple to implement, as stdout is only shown on a test failure, so we could just preemptively print a playground link and it'll show up on a test failure.
Playground links pass the code via a base64 encoded string appended to the url after a #. Therefore we could do something like:
format!("http://localhost:3000/#{}", code)
Note that we produce a localhost link, because play.rome.tools is main by default. We could also print out a command for starting the playground if necessary.
The text was updated successfully, but these errors were encountered:
@NicholasLYang is the goal to create these links on CI test failures? It will be hard for others to contribute this behaviour because they aren't allowed to run CI jobs.
Description
Currently when I debug a failing test, I have to copy the code into a playground manually. Instead, we could have the link automatically generated. This could be pretty simple to implement, as stdout is only shown on a test failure, so we could just preemptively print a playground link and it'll show up on a test failure.
Playground links pass the code via a base64 encoded string appended to the url after a
#
. Therefore we could do something like:Note that we produce a localhost link, because play.rome.tools is main by default. We could also print out a command for starting the playground if necessary.
The text was updated successfully, but these errors were encountered: