@diosmosis opened this Issue on November 11th 2014 Member

This metadata is used only by the Actions API and is only handled by getProcessedReport and Visualization.php. Handling it in "raw" API consumers makes mostly complicates the consumer code for small functionality that is only used by a handful of reports. Instead, the logic can be moved to Report metadata classes. The visualization code can be put in the Report::configureView method for reports that need to remove columns and the processed report logic can perhaps be put into a new Report::configureForApi method.

Powered by GitHub Issue Mirror