Fairly easy to get around and continue without local caching but it led me to do a bit of reading on [disabling] graph introspection which seems to be up for some debate. I'm wondering why you chose to disable it.

Thanks for the feedback @dabombace ! We actually chose to disable it for security purposes. Our most recent pen-test suggested that the graphQL introspection queries might pose an unnecessary risk related to enumerating fields and allowing for DOS attempts

Interesting for sure. I would interpret that as a pretty strong repudiation of graphql in general then.

I wouldn't necessarily say that - I think there are just different tools for different jobs. It really depends on your call patterns. Graphql can be useful with FHIR when you have a number of Resources that are linked to each other

Thanks for the info. I'm gonna keep trucking along w my flutter app and messing around with the graph apis no local cache for now.

@dabombace We statically pre-generate the schema. It is available here: https://graphiql.medplum.com/schema/schema-v1.json

Yea, having it disabled thus not having clients requesting the type info probably means better performance and scaling not withstanding any security concern.

Something totally new will come around right when we solve all of the graphql problems