You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues for this feature request and I know that duplicates will be closed
Is your feature request related to a problem?
GraphQL collections have the ability to create forks, but none of the other features that make them useful, including the ability to pull changes or make pull requests. This seems like an grossly incomplete feature that should not have been released yet if this is the case.
Describe the solution you'd like
GraphQL collections should offer the same capabilities, as GraphQL requests using Postman's regular HTTP request interface. Forked GraphQL collections do not offer the ability to pull changes or create pull requests.
Standard collection context menu
GraphQL collection context menu
Describe alternatives you've considered
No response
Additional context
I think the confusion would be removed if you remove the "Create a fork" option from GraphQL collections until the feature is complete. There is no purpose in forking a collection if you cannot pull changes or create pull requests. Removing this option would inform users to export/import the collection instead.
The text was updated successfully, but these errors were encountered:
Is there an existing request for this feature?
Is your feature request related to a problem?
GraphQL collections have the ability to create forks, but none of the other features that make them useful, including the ability to pull changes or make pull requests. This seems like an grossly incomplete feature that should not have been released yet if this is the case.
Describe the solution you'd like
GraphQL collections should offer the same capabilities, as GraphQL requests using Postman's regular HTTP request interface. Forked GraphQL collections do not offer the ability to pull changes or create pull requests.
Standard collection context menu
GraphQL collection context menu
Describe alternatives you've considered
No response
Additional context
I think the confusion would be removed if you remove the "Create a fork" option from GraphQL collections until the feature is complete. There is no purpose in forking a collection if you cannot pull changes or create pull requests. Removing this option would inform users to export/import the collection instead.
The text was updated successfully, but these errors were encountered: