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
templating #35
Comments
I'd be in favor of dropping the template-related code and document that graphite-api doesn't have templates and passing |
why? i would argue that templates are quite useful, and easy to implement. |
Dieterbe
pushed a commit
to Dieterbe/graphite-api
that referenced
this issue
Sep 2, 2014
similar to previous PR, except now it integrates into the main yaml file instead of a separate graphTemplates.conf
Dieterbe
pushed a commit
to Dieterbe/graphite-api
that referenced
this issue
Dec 14, 2014
similar to previous PR, except now it integrates into the main yaml file instead of a separate graphTemplates.conf
vladimir-smirnov-sociomantic
pushed a commit
to vladimir-smirnov-sociomantic/graphite-api
that referenced
this issue
Dec 30, 2014
similar to previous PR, except now it integrates into the main yaml file instead of a separate graphTemplates.conf
bogus-py
pushed a commit
to bogus-py/graphite-api
that referenced
this issue
Aug 27, 2015
similar to previous PR, except now it integrates into the main yaml file instead of a separate graphTemplates.conf
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
in
graphite-web/webapp/graphite/render/glyph.py
the methodloadTemplate
reads the template from the config file. graphite-api doesn't do this.template
http param and graphTemplates.conf, glyph.py also refers to the file, but the file is not used and the param does nothing.The text was updated successfully, but these errors were encountered: