wadjeroudi

@dunglas I've the same problem. I think your solution using the security.yml will only deny if no https is used. Maybe you should use https://symfony.com/doc/current/routing/scheme.html But don't know how to...

when a feature is unleashed to all users, what would be the process ?

@vvasiloi can you be more precise about your implementation plz ? previously, you advocated for an external solution via plugins.

Same kind of problem, but the selected value is the wrong one, it should show 16 and 8 : https://jsfiddle.net/98618fru/

Fixed from v2.3.1 here https://github.com/Semantic-Org/Semantic-UI/issues/6123

@bartoszpietrzak1994 It was on purpose, I deleted the validation file that already existed in my PR to disable the validation globaly. If we need to keep the xml validation, the...

@loevgaard seems ok now. I wanted to stop at 10, but impair is better (too stubborn to launch the CI locally :$) There's an issue with psalm ?

@ErikPetersenDev running in this issue, could you propose a solution for the setAll issue ? In the last updated doc, it still has the setAll call on the new response...

same issue using the new middleware  ```js export async function getProjectById(id: string, type: string): Promise { const supabase = createClient(); console.log('get ID', id, type) console.log('get USER', await supabase.auth.getUser()); ```...

no problem locally, it happens on vercel because of their serverless function and limitation. calling from a server component (getUser is called inside getProjectById) ```js export default async function ProjectPage({params}:...