Discussions and the REST API vs GraphQL API

[SlyckLizzie]

Why is it that the repository update and create REST APIs don't implement the has_discussions property, even though the get call shows it and the "Create a repository for the authenticated user" call allows it? I have read that you can only set this flag through the GraphQL API. If this is true it makes no sense since the GraphQL repository input only covers the basic repo edit parameters (about 5 or 6) and nothing else. That means one has to bounce between different API projects, which have different scopes, rate limits, etc, in order to be able to fully update a repository programmatically. It would make more sense to me if the GraphQL API supported all of the other repository settings, but it is far from that.

Can someone explain to me the illogical setup of this and why a simple update flag implementation for has_discussions has not been done?

I see a lot of inconsistencies between REST calls that implement the same basic objects.