Ivo Sabev

+1

+1

Any movement on this issue?

+1

I am using this regexp: ```js const formatted = "\x1b[F\x1b[31;1mHello, there!\x1b[m\x1b[E"; const text = formatted.replace(/[\u001b\u009b][[()#;?]*(?:[0-9]{1,4}(?:;[0-9]{0,4})*)?[0-9A-ORZcf-nqry=>

I am paying for PRO and can't use it because it was not simultaneously released in all FontAwesome packages. 🤦‍♂

This should be somewhere in the docs, also props support was what I was originally looking for. Thanks!

+1 fo this, it is very common scenario. For example I have a `orderSchema` and I have an `updateOrder()` function that takes `orderSchema.partial()` (listing each key in the `partial()` function...

Why is this not maintained and updated for the latest Apollo API, since SSE is in most cases superior to WebSocket?

Validation errors are coming from the POST response, so the other two GET requests seem unnecessary and I agree there should be an opt-out of them.