Sandro Circi

I only now had time to upgrade from `2.0.10` to `2.0.17` and can also confirm it seems to be fixed. Tested with Nuxt: - local components - remote components (layers...

@kingyue737 I might be wrong, but it seems to me an extension conflict. Could you quickly test disabling all the extension but `Vue - Official`? (I also imagine your `ctrl+j`...

I was creating a reproduction for another issue when I've discovered this bug. I already have the reprod ready but I need to polish couple of things before pushing it....

Ok, I finally managed to polish the reproduction and make it as simple as possible. It deploys a local directus stack using docker. The reproduction is part of the [directus...

With the solution from #18706, if you uncomment the `user` and `command` lines inside the `docker-compose-dev.yml (that automatically apply a `schema.yml` at container start) you can see that we don't...

I'm noticing that the FORBIDDEN error only occurs if the `schema apply` is done **AFTER** the `directus start`. In fact, if I do: 1. run Directus 2. apply the schema...

I was minding my own business in 10.2.1, when erroneously I've started up directus before applying the schema, and discovered something curious: Singleton collections show up like this:  So...

> With the solution from #18706, if you uncomment the `user` and `command` lines inside the `docker-compose-dev.yml (that automatically apply a `schema.yml` at container start) you can see that we...

> Odd! That indicates to me that it might be something in the caching of the schema information, rather than the schema itself 🤔 Reordering or making any other alterations...

Although I'm new to the project I wasn't expecting to see these features missing. The performance impact of futures and functions do vary too much to be reliable (not to...