Grafanano signalmediumCluster of 8 signals
Card #3579 · Grafana

Steep learning curve and poor documentation for Angular plugin development

Developers struggle to build plugins due to a lack of clear documentation on using Angular and custom directives. Newcomers are often confused by the distinction between AngularJS and Angular 4, creating a high barrier to entry for community contributors.

GrafanaUpdated 1d ago0.18
Pain score
0.18/ 1.00 · weighted product of four components
Reach1.00
distinct authors (log-normalized)
Recency1.00
freshness decay, half-life months
Engagement0.43
upvotes + comments, normalized
Monetization0.25
willingness-to-pay cues in evidence
§ Evidence — 3 verified quotes
This is a frustratingly high barrier to entry as someone who’s trying to contribute to the community and add functionality to Grafana by building a new datasource plugin
Forum·@jkirsop··source ↗
It would be really helpful if AngularJS was mentioned instead of just Angular in the tutorial for developing a plugin , as newcomers (like me) may not know when it was developed and be misled too.
Forum·@jandro··source ↗
I need to add my own directives but I can’t figure out how to do this properly in the setup here. Is there a simple example of plugins creating directives?
Forum·@digant··source ↗

Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.

Upgrade to Pro