You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Havent properly decided how/what I want to do yet, but for the purposes of getting a proof-of-concept the current pages use PHP/Twig to write inline javascript for rendering graphs. 🤢
Ideally I want this to be something I can just hit and pull json from to populate the graphs. This would ultimately allow me a lot more flexibility with how the graphs work.
I think the simplest initial revision would be a basic API of sorts that would have a number of "views" defined - each view representing the data required to display one graph. The only issue with this method is 1 page view with say 30 graphs would result in 30 additional hits to the "graph api" which might hamper performance/usability a bit.
Will need some additional testing
Happy to take discussion/suggestions on this
The text was updated successfully, but these errors were encountered:
Havent properly decided how/what I want to do yet, but for the purposes of getting a proof-of-concept the current pages use PHP/Twig to write inline javascript for rendering graphs. 🤢
Ideally I want this to be something I can just hit and pull json from to populate the graphs. This would ultimately allow me a lot more flexibility with how the graphs work.
I think the simplest initial revision would be a basic API of sorts that would have a number of "views" defined - each view representing the data required to display one graph. The only issue with this method is 1 page view with say 30 graphs would result in 30 additional hits to the "graph api" which might hamper performance/usability a bit.
Will need some additional testing
Happy to take discussion/suggestions on this
The text was updated successfully, but these errors were encountered: