Graphql config file now seems to be a requirement

Today we randomly started hitting an error about use_natural_pluralization and that it cannot be set to false, or something similar. We have had our realm/appservices config for years, and recently updated it (maybe 3 months ago) to appservices. Today we hit this error and to solve it, I had to add a graphql/config.json file with the contents of {"use_natural_pluralization":true}.

I think this is weird and must be a bug on the service’s side because we don’t use graphql. I just thought I would point this out that it will break a lot of people’s deployments. I would suggest that, when your service does not see a graphql config file, it does not try to set new values, or whatever it does. If that file is not being pushed, just… don’t do anything.