-
Notifications
You must be signed in to change notification settings - Fork 176
Don't merge mixins in the global namespace anymore. #234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Instead, put them in the $.mixins map. This allows for mixins to be places in specific Grafana directories, and also removes the horrible bug around playbook links. Still support merging into the global namespace for the time being, but this will be going away. Signed-off-by: Tom Wilkie <[email protected]>
Signed-off-by: Tom Wilkie <[email protected]>
7a8d3f4 to
c5f5998
Compare
Signed-off-by: Tom Wilkie <[email protected]>
c5f5998 to
5b13029
Compare
Signed-off-by: Tom Wilkie <[email protected]>
Signed-off-by: Tom Wilkie <[email protected]>
tombrk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! You could add some comments to the foldr functions explaining what's their purpose.
Also I'd like to wait @malcolmholmes review, as he's currently rewriting parts of this lib as well, just to make sure these don't interfere
Signed-off-by: Tom Wilkie <[email protected]>
|
But the You could say, the current approach is that Which is a more conventional programming model. Because the |
|
@malcolmholmes said
|
Instead, put them in the $.mixins map.
This allows for mixins to be places in specific Grafana directories, and also removes the horrible bug around playbook links.
Still support merging into the global namespace for the time being, but this will be going away.
NB this also removes the old field names (
grafana_dashboards), I couldn't find a mixin that used this anymore.Signed-off-by: Tom Wilkie [email protected]