-
Notifications
You must be signed in to change notification settings - Fork 520
Add url paths on the tye.yaml to make it easier to navigate to available endpoints #618
Comments
@davidfowl / @jkotalik - could we look at Routes and provide these in the dashboard without having to define them explicitly? |
No, routes are part of the application. There's no way to get that information statically from outside the app. |
+1 for this. I'm writing a set of microservices that do not have coupling between them (no REST endpoints) but instead use a shared messagebroker for all actions. As such, it'd be nice to have all my services point straight to their /graphql endpoint when clicked from the tye dashboard. This is an important feature to add. It can be read from the launchSettings.json in the property "launchUrl" |
+100 for this! Judging by the time this issue was created...holding our breath could get us killed. |
Pull requests are also a thing 😉 |
I bet you couldn’t hold it…same as me🤣 |
Believe it or not, I was going to ask if anyone was working on this. You beat me to it, @ante-maric. 😉 I wanted to discuss some finer details too, like how about Example. This configuration (note I didn't include a hyphen in the
would produce something like this:
|
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. |
What should we add or change to make your life better?
The idea is to have something like this on the
tye.yaml
This would then be exposed on the dashboard as URLs. e.g.
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.
The text was updated successfully, but these errors were encountered: