Add url paths on the tye.yaml to make it easier to navigate to available endpoints

What should we add or change to make your life better?

The idea is to have something like this on the tye.yaml

- name: results
  project: results/results.csproj
  -paths: /swagger;/hangfire;/lively;/page=2&pageSize=10

This would then be exposed on the dashboard as URLs. e.g.

• https://localhost:5001/swagger
• https://localhost:5001/hangfire
• https://localhost:5001/page=2&pageSize=10

These can be ignored during deployment.

Why is this important to you?

This would make it easier to simply navigate to endpoints that you want to use in that service and save a couple of keystrokes.

[ante-maric]

I have investigated a little bit, investigation turned into actual code change and in no time I got it working on my machine.

@ignacioerrico I would also prefer routes over paths. Regarding a way to display the links…connectionStrings are also displayed in Bindings column, so that needs to be taken into account.

[davidfowl]

Pull requests are also a thing 😉