Vinh
> I know that already exists some library that simply does mere type extraction from a typescript source. I am interested in this project for the exact purpose of type...
Thanks, I'll check it out!
Thanks for pointing this out! We have added a story ticket in our backlog. As you said, the misbehaving browsers are not in our supported browserlist, so this will have...
Running into the same issue! Very easy to reproduce, just run: ``` ➜ SET bugtest 🫠 OK ➜ GET bugtest Bad escaped character in JSON at position 12 ```
I think I ran into this, I tried to do this: ```jsx {"Signed in as ."} ``` ```fluent comments-userBoxAuthenticated-signedInAs = Signed in as . ``` But the `.` is swallowed...
> Do you think that using is an acceptable work-around? It's not pretty, and it goes against user expectations. The workaround is simple and functioning though, however I'd like to...
We have some tests that stubs the props data of e.g. Fragment Containers. The types were failing since I upgraded because of `$fragmentRefs` and `$refType` which weren't there before. My...
Agree. I'm a bit sceptical with using a different set of types for tests though, it sounds like a configuration nightmare. Btw I simplified the above solution a little bit:...
Not sure if I can follow your idea, we use the generated types in our props so they already include the fragmentref related props. Even if we could have the...