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
generating a scenes app with backend results in a main.go with a different name as the plugin-id
What you expected to happen
the plugin-id should probably match src/plugin.json
How to reproduce it (as minimally and precisely as possible)
In this environment...
Node 20
With this config...
npx
Run '...'
❯ npx @grafana/create-plugin@latest
Need to install the following packages:
@grafana/create-plugin@4.1.0
Ok to proceed? (y) y
✔ What is going to be the name of your plugin? · pleasework
✔ What is the organization name of your plugin? · briangann
✔ How would you describe your plugin? · something
✔ What type of plugin would you like? · scenesapp
✔ Do you want a backend part of your plugin? (y/N) · true
✔ Do you want to add Github CI and Release workflows? (y/N) · true
✔ Do you want to add a Github workflow for automatically checking "Grafana API compatibility" on PRs? (y/N) · true
Which package(s) does this bug affect?
Package versions
What happened?
generating a scenes app with backend results in a main.go with a different name as the plugin-id
What you expected to happen
the plugin-id should probably match src/plugin.json
How to reproduce it (as minimally and precisely as possible)
Node 20
npx
This doesn't appear to cause any issues running the plugin, but there is a disconnect in naming, and also the container_name.
The validator (and gcom) doesn't understand
-scenesapp
as a suffix, we should probably just use-app
here.Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: