{"action":"created","issue":{"url":"https://api.github.com/repos/graphql-python/graphene/issues/813","repository_url":"https://api.github.com/repos/graphql-python/graphene","labels_url":"https://api.github.com/repos/graphql-python/graphene/issues/813/labels{/name}","comments_url":"https://api.github.com/repos/graphql-python/graphene/issues/813/comments","events_url":"https://api.github.com/repos/graphql-python/graphene/issues/813/events","html_url":"https://github.com/graphql-python/graphene/issues/813","id":350847134,"node_id":"MDU6SXNzdWUzNTA4NDcxMzQ=","number":813,"title":"Commercial support?","user":{"login":"leebenson","id":719722,"node_id":"MDQ6VXNlcjcxOTcyMg==","avatar_url":"https://avatars3.githubusercontent.com/u/719722?v=4","gravatar_id":"","url":"https://api.github.com/users/leebenson","html_url":"https://github.com/leebenson","followers_url":"https://api.github.com/users/leebenson/followers","following_url":"https://api.github.com/users/leebenson/following{/other_user}","gists_url":"https://api.github.com/users/leebenson/gists{/gist_id}","starred_url":"https://api.github.com/users/leebenson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/leebenson/subscriptions","organizations_url":"https://api.github.com/users/leebenson/orgs","repos_url":"https://api.github.com/users/leebenson/repos","events_url":"https://api.github.com/users/leebenson/events{/privacy}","received_events_url":"https://api.github.com/users/leebenson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-08-15T15:10:29Z","updated_at":"2018-09-04T12:30:52Z","closed_at":null,"author_association":"NONE","body":"I love this lib - thanks so much for your hard work, @syrusakbary!\r\n\r\nWith that said, I'd happily contribute to paying for more of your time to extend Graphene, and fill in a few missing pieces that would make it more viable to use in production.\r\n\r\nNamely:\r\n\r\n- Error catching, per https://github.com/graphql-python/graphql-core/issues/177, and https://github.com/graphql-python/graphql-core/issues/202. System exceptions bubble up to user output by default, which a dangerous default IMO. I'd love to see a cleaner way of logging exceptions and controlling error output that could be defined in one place, rather than defensive `try/except` blocks in every mutation.\r\n\r\n- Core improvements / re-factoring. Thread safety (#43), resolving promise issues (https://github.com/syrusakbary/promise/issues/57), moving to `async/await` per [your comment](https://github.com/graphql-python/graphene/issues/612#issuecomment-347066815), etc. There are a few core things that are beyond my immediate experience with how things work under the hood, that seem like they have some potential to throw weird/unexpected issues that are hard to diagnose.\r\n\r\n- Documented subscription support/patterns, per #781.\r\n\r\n- Docs synced with releases. There have been a few occasions where trying doc examples has thrown errors, such as #812 today or https://github.com/graphql-python/flask-graphql/issues/52 which I ran into a few days ago. When this happens, monkey-patched workarounds are usually suggested by the community, which makes for brittler code.\r\n\r\n- Some more tooling to provide official solutions for #772, etc. Calculating the cost of queries, parsing the AST tree and preempting query joins that might be necessary, etc. Outside the purview of the core, perhaps, but necessary stuff at scale that would save devs reinventing the wheel.\r\n\r\n- Closing issues faster. This is just a general thing, but there are issues going back 2-3 years that would be good to get unstuck. Much of it might even be redundant now or have other solutions, but clearing the backlog would make a clearer case for using the lib in production, knowing those same issues are unlikely to resurface.\r\n\r\nObviously, your time is valuable and the fact that you've put together _anything_ at all - let alone something as cool as Graphene - is amazing, so thank you.\r\n\r\nBut perhaps there's a way, as a community, we could buy more of your time to address some of the above? I'd happily chuck in a few bucks on the reg to keep this lib up-to-date."},"comment":{"url":"https://api.github.com/repos/graphql-python/graphene/issues/comments/418349174","html_url":"https://github.com/graphql-python/graphene/issues/813#issuecomment-418349174","issue_url":"https://api.github.com/repos/graphql-python/graphene/issues/813","id":418349174,"node_id":"MDEyOklzc3VlQ29tbWVudDQxODM0OTE3NA==","user":{"login":"syrusakbary","id":188257,"node_id":"MDQ6VXNlcjE4ODI1Nw==","avatar_url":"https://avatars2.githubusercontent.com/u/188257?v=4","gravatar_id":"","url":"https://api.github.com/users/syrusakbary","html_url":"https://github.com/syrusakbary","followers_url":"https://api.github.com/users/syrusakbary/followers","following_url":"https://api.github.com/users/syrusakbary/following{/other_user}","gists_url":"https://api.github.com/users/syrusakbary/gists{/gist_id}","starred_url":"https://api.github.com/users/syrusakbary/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/syrusakbary/subscriptions","organizations_url":"https://api.github.com/users/syrusakbary/orgs","repos_url":"https://api.github.com/users/syrusakbary/repos","events_url":"https://api.github.com/users/syrusakbary/events{/privacy}","received_events_url":"https://api.github.com/users/syrusakbary/received_events","type":"User","site_admin":false},"created_at":"2018-09-04T12:30:52Z","updated_at":"2018-09-04T12:30:52Z","author_association":"MEMBER","body":"I'm working towards what we talked here 😊\r\n\r\nThese are the most recent changes:\r\n* Added ROADMAP file in the project repo (and link it from the README)\r\n  https://github.com/graphql-python/graphene/blob/master/ROADMAP.md\r\n* Added TEAM page in Graphene website (so it's easier to see main contributors of the community)\r\n  https://graphene-python.org/team/\r\n* Added a support page in Graphene (is hidden right now, will be enabled once we are all happy with the current framework)\r\n  https://graphene-python.org/support-graphene/\r\n* Created Patreon page \r\n  https://www.patreon.com/syrusakbary\r\n\r\nIf you could visit the [Patreon page](https://www.patreon.com/syrusakbary), the [Graphene support page](https://graphene-python.org/support-graphene/) and write here your feedback, it would be highly appreciated!\r\n@codeocelot @leebenson @patrick91 \r\n\r\n*PS: I will update the ROADMAP with your suggestions towards specific issues / features you would like to see in the GraphQL Python community moving forward, so we make sure the funding will enable those*"}}
{"actor":{"display_login":"syrusakbary"}}