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
I accidentally created an API with the same base URL as another via the interactive restish api configure and afterwards I cannot interact with restish api in any way due to the following panic:
panic: multiple APIs configured with the same base URL: <BASE URL VALUE>
goroutine 1 [running]:
github.com/danielgtaylor/restish/cli.initAPIConfig.func6(0x1400083fbf0?, 0x1400083fb90, 0x1400007c3c0)
/home/runner/work/restish/restish/cli/apiconfig.go:245 +0x204
github.com/danielgtaylor/restish/cli.initAPIConfig()
/home/runner/work/restish/restish/cli/apiconfig.go:261 +0x960
github.com/danielgtaylor/restish/cli.Init({0x103094b9b, 0x7}, {0x10334a270, 0x6})
/home/runner/work/restish/restish/cli/cli.go:571 +0x1f68
main.main()
/home/runner/work/restish/restish/main.go:25 +0x1b8
I was able to fix this by manually editing the JSON file after digging it up, however it would be helpful if at least the api edit command could open an invalid config to make fixing this easier. Alternatively, api configure could check to see if the base URL entered is a duplicate and refuse to write.
Please let me know if more info is needed.
Thanks!
restish version 0.20.0
The text was updated successfully, but these errors were encountered:
I accidentally created an API with the same base URL as another via the interactive
restish api configure
and afterwards I cannot interact withrestish api
in any way due to the following panic:I was able to fix this by manually editing the JSON file after digging it up, however it would be helpful if at least the
api edit
command could open an invalid config to make fixing this easier. Alternatively,api configure
could check to see if the base URL entered is a duplicate and refuse to write.Please let me know if more info is needed.
Thanks!
restish version 0.20.0
The text was updated successfully, but these errors were encountered: