Joost

i was also trying something like that so users dont need to provide the open api key. But i found this and wonder if its even legal [https://replit.com/bounties/@SamuelSmith68/automate-openai-acco?t=applications](https://replit.com/bounties/@SamuelSmith68/automate-openai-acco?t=applications)

Im experiencing the same issue with active routeEnhancers, but i dont get the same error message. In my case somehow the detailAction is called an then caught by the handleNoNewsFoundError...

I ended up using two different routeEnhancers. One for the detail controller and one for all views with the list controller. Somehow news detail and category list where overwriting each...

Hi Simon, Thanks for your quick response. I already took a look into your [named slots PR](https://github.com/TYPO3/Fluid/pull/1118), and while it’s a great addition, I think it tackles a slightly different...

Yeah i know that, looking forward to the `argumentsAs` feature :)

It's mainly just a `context` variable, I guess, so this addition should work :) Keeping the outer rendering context and its variables definitely makes sense. 👍

Hey @mkroener im creating fluid-primitives and if i understand you correctly the custom component renderer from fluid-primitives is already doing what you described like simon explained it (just not yet...

Hi, i totally understand your hesitation. Something like a "scope" sounds nice, i initially thought this would be a little bit to specific to my usecase but i think more...

I think `tags` would be a nice option. I updated the pr :)

Hi, i think annotation is indeed a better naming. The API seems nice but i have some questions: Is the `exposeToClient` part from the `f:annotation` ViewHelper some arbitrary value or...