Ryan Weaver

Thanks for all the extra info! > We also tried Turbo to add some sub-component (push a "notification" component in a list) but we have some checksum problems Can you...

I like this idea!

Hi @janklan! Thanks for bringing up this situation :). So, if I understand it correctly, your (initial) goal is pretty simple: create an autocomplete, but one that uses your custom...

> Either way, I think it's all doomed anyway: The $organisation is derived from the current context when the form field is generated, and when the autocompleter request is made,...

Thanks Jan!

I did a deploy today... and I must've broken something! The error is: > {"message":"Matched route \"app_turbo_chat\".","context":{"route":"app_turbo_chat","route_parameters":{"_route":"app_turbo_chat","_controller":"App\\Controller\\TurboController::turboChat"},"request_uri":"https://ux.symfony.com/turbo/chat","method":"POST"},"level":200,"level_name":"INFO","channel":"request","datetime":"2022-08-25T00:38:39.168688+00:00","extra":{}} {"message":"Uncaught PHP Exception Lcobucci\\JWT\\Signer\\InvalidKeyProvided: \"Key provided is shorter than 256 bits, only 224...

It looks very nice. My only pushback might be that a UX component could be overkill. From a quick look at the docs, you set it up via: ```js import...

How would this work with exposed properties? Like, if “title” is exposed, i guess the security check would still be applied only to the top-level post, right? I also think...

Hmm. I'm not sure about the best solution here! My initial reaction is that our CSS should add `!important` on it. So: ``` [data-loading=""], [data-loading="show"], [data-loading="delay|show"] { display: none !important;...

Hi there! This... MAY be possible, but indeed, it's difficult, which is why we currently require you to have a separate field. The tricky thing is that, in order for...