Alen Turkovic

> If it is anything like https://github.com/desmondw/snowflake then I would imagine that the CSS selector will be copied to the clipboard when the user clicks on an element while the...

My target audience are people who are not very technically proficient but are still somewhat technical. They are a support team that needs to frequently configure CSS selectors for our...

Did you make any further progress on this?

Is this likely to become a new feature in the next release? Also, specifying different input for mutations is super convenient, but the current solution you proposed requires us to...

I was reading about some GraphQL best practices and I like the idea of all mutations having a single input object type: https://medium.com/graphql-mastery/json-as-an-argument-for-graphql-mutations-and-queries-3cd06d252a04 https://graphqlmastery.com/blog/graphql-best-practices-for-graphql-schema-design > Not sure I'm getting this...

I am afraid I am still not following, most likely due to lack of documentation and examples, so I am probably misusing things. This is also the first project I...

Yes, that's exactly what I meant. The last chapter is only about allowing to configure the `Pool` from within the CSF, but what you said to distribute that responsibility externally...

Great :) I was mainly worried about backwards-compatibility of such changes.

> > > It's not (yet) clear to me how an externally configured pool gets access to internal SF to get new sessions (unless separately configured there too, which makes...

I did not test it, I am a bit overwhelmed at the moment, but I think if you set retry period to longer than the timeout period, it should do...