"Exposed Schema and Resource Attacks" - uhm.. I feel like a system should be able to detect and throttle clients who are abusing their fair share, regardless of whether clients are fully aware of the internal structure of data - if graphql prevents you from introducing such throttling behavior, it really seems like not a good fit for a serious production environment
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"Exposed Schema and Resource Attacks" - uhm.. I feel like a system should be able to detect and throttle clients who are abusing their fair share, regardless of whether clients are fully aware of the internal structure of data - if graphql prevents you from introducing such throttling behavior, it really seems like not a good fit for a serious production environment