Subtask of #79550: Automate gathering of quality metrics and Project metrics for drupal.org redesign:
Once we decide on a data storage plan (#889890: Finalize and implement data storage plan for project_metrics) we need to expose this data to views. Depending on how #889890 turns out, this will probably be a somewhat tricky task to dynamically loop over all our tables and expose them nicely. I bet there'd some goodness in Table Wizard that we can learn/lift from. ;)
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | metrics_times-views.patch | 3.21 KB | mikey_p |
Comments
Comment #1
hunmonk commentedwould it be beneficial to have table wizard as a dependency? just thinking there's no need to re-implement the wheel if it's not necessary.
Comment #2
dwwre: table wizard as a dependency ... -1 to that:
A) I don't think the infra team is going to be too psyched about tw on d.o
B) We don't need all of tw -- I just meant we should learn something from how it works instead of starting over from scratch
C) I have a (completely unsubstantiated) feeling that it would make the default views even harder, since it's yet another step removed and run-timey and dynamic and all...
That said, if you can get killes/drumm et al to agree on (A), and Moshe et al can help sort out (C) so it's a non-issue, I'm fine with going that route. I just think it's overkill and actually adds complication. But I could be wrong about this.
Comment #3
hunmonk commentedno official project exists for this module yet. moving to redesign queue for now, and retagging
Comment #4
mikey_p commentedComment #5
mikey_p commentedHere's an initial patch. I'm currently researching if there is a way to implement this without exposing each metric as it's own base table for views. This rather pollutes the UI when creating a view and just seems kludgy.
Comment #6
hunmonk commentedmoving this issue to the new module's home...
Comment #7
hunmonk commentedinitial views support has been completed, tested and working, and committed to the module.