tech-insights: Move TechInsightCheck to @backstage-community/plugin-tech-insights-common #1527
Open
2 tasks done
Labels
enhancement
New feature or request
Plugin Name
tech-insights
🔖 Feature description
Actually, it is not a feature, but I could not find a more fitting plugin-related option when openning a new issue.
The type
TechInsightCheck
is exported from@backstage-community/plugin-tech-insights-node
. But it has nothing that is exclusive to the node envionment. Moving it to@backstage-community/plugin-tech-insights-common
makes it accessible in more places.🎤 Context
Just to give a use case as an example, in our Backstage instance we have a
-common
isomorphic plugin for defining types and common values about our custom tech insights checks. Right now we have to copyTechInsightCheck
to it so that we can extend it with ourCustomTechInsightCheck
type. This type includes extra information that can help UI (like grouping information, a short name for table views, …) so frontend application importes and usesCutomTechInsightCheck
. That’s why this type should be in a-common
package and that’s also the reason it is not possible to importTechInsightCheck
from its current package.✌️ Possible Implementation
I would be happy to create a PR if the change makes sense to you.
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: