Consider renaming "resource" to "route" about grafana-plugin-sdk-go

[bergquist]

I approve of this message.

[marefr]

Reason for resources: https://restful-api-design.readthedocs.io/en/latest/resources.html. Route is to me a technical thing and you could register such using the SDK. Due to this I would vote for something else than route. But I really don't care as long as the only thing that changes is the route. I feel currently there are other things more important to focus on.

[ryantxu]

This is just a naming discussion -- no functional changes. neither is perfect, but resource is tooo general, and I find the plural api path:

apiRoute.Any("/datasources/:id/resources/*", ...

pretty akward

[kylebrandt]

If we can I would like to see us add Route/Paths to DataQuery as well. If we can do that, this name might be more confusing?

[bergquist]

I feel currently there are other things more important to focus on.

Now is our chance to make breaking changes to the protobuf files. After 6.7 we have to stick with them FOR EVER :) That said.. even thou I prefer route I'm not sure it's worth the effort. It's not that much better.

For DataQuery I think Paths would make sense and I dont think renaming resources to routes would be confusing.

[ryantxu]

i think this ship sailed.... :(