This. Choose your destiny:
1. Take time to review the code, post it to the author with knowing that nobody and nothing is going to learn from it except for you doing his job for feeding new prompts
2. Take ownership of the branch and fix the AI code
3. Read through the code to get some learning out of it if possible, close the PR and write your own
lead engineer of unchained engine here. still using apollo client for client projects but i stopped using apollo server because you guys started to put important security features behind your paywall for example whitelisting persistent queries (pql). that makes it difficult trust-wise.
I'm an engineer on the client team, so I'm a bit fuzzy on the Apollo Server details and history, so please bear with me :)
I guess you're talking about [Safelisting Persisted Queries](https://www.apollographql.com/docs/graphos/platform/security...) here.
Afaik, if you want to use the full integration with the GraphOS platform, you'll need an account with us. The feature is supported on the free account with a rate-limit, and if you would need more, you could go with the "developer" account, which we launched this summer, which is quite reasonably priced and comes with starting credits: https://www.apollographql.com/pricing
That said, Apollo Server is open source and at no point you are locked into our platform - it's just that our platform takes a lot of work away from you, allowing you to manage those whitelists easier.
If you want to manage your whitelist yourself, it's totally doable - I just did a quick google search and have come up with more than a dozen articles describing various ways of doing it.
Just be aware that there is a lot of coordination between builds and deployments going on, quickly leading to very complex setups - which is why we offer the platform integration in the first place.
So I think the idea was not to lock anyone out of these features, just create a quick pit of success by making the GraphOS integration really easy - but I can see where your feelings are coming from. I hope we can earn back your trust over time!
Not sure, even then, doesn‘t reflog keep it quite a while locally on the machine that the force push was sent? Maybe he did not commit his changes for a month and sent a git reset —-hard
