4 ms·
Eeeeh, I hit the question of if I should take an approach like that recently and I think that writing out a custom format like that makes your code brittle and
by munk-a 7y ago
Eeeeh, I hit the question of if I should take an approach like that recently and I think that writing out a custom format like that makes your code brittle and is generally poor at scaling across endpoints. We were actually considering one of the graphQl look-a-likes to step directly into a pre-rolled format for declaring the fields expected in the response rather than roll our own format.
You absolutely can define reports as graphQl entities (and really, table -> entity mapping should never be 1to1) and just let users leverage the field filtering component of the transit format.
Lastly, PHP is pretty sweet now a days you should give it a try!