-
Notifications
You must be signed in to change notification settings - Fork 477
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
Charts not visible #101
Comments
Hey @seanfcarroll, please read the docs before filing issues: https://github.com/ankane/blazer#line-chart |
Hi there, thanks for the quick response. I think I am being dumb ... I have a count in my query, but no chart appears
|
OK I found the problem. The submission_time field is timestampz ie: timestamp with timezone (on Postgres). When I run against a timestamp field eg: created_at, it works. |
Sorry @seanfcarroll, think I was in a bad mood on Monday. Both timestamp and timestamptz should work. The time column must come first, then the numeric. I'll make the docs more clear. |
Hey @ankane no problem. This is a great gem, and I'll soon do some work to help you out. I can start with #97 and perhaps also #98. I think it would be great to able to drop Blazer into an existing Rails app, also noted here #49 and here #50 I have included it into an app, but needed to hack the layout a bit to include it in the same layout. Different engines approach the problem in different ways. I think the Devise approach is the gold standard, for gems without much markup or structure. I also like the Thredded approach including the ability to override the layout from the initializer. The other thought I had was to add an advanced chart, where the user can write the SELECT first, then chose from the returned columns for x and y axis on a chart. I can start working on some or all of these. My own project is crowdAI and we will probably add Blazer into here also. |
I'm on Rails 5 -- rails (5.0.0.1), no console errors but no chart at all.
(Note I have temporarily rolled back the changes I described in #50, so am using Blazer, I think, out of the box)
The text was updated successfully, but these errors were encountered: