Re:Why not use GraphQL?
by andrewingram on Saturday November 07, 2020 @06:02PM
(#25020569)
Redesigns, UX changes etc, will all change how a UI interacts with data but won't necessarily require any changes to the underlying data model.
Adding brand new capabilities to a system (or refactoring existing ones) will usually requires changes to the GraphQL layer, but this is only a subset of frontend work. Iterating on what already exists also represents a lot of development time.
Adding brand new capabilities to a system (or refactoring existing ones) will usually requires changes to the GraphQL layer, but this is only a subset of frontend work. Iterating on what already exists also represents a lot of development time.