Hey there!
First, thank you! Very nice work!
Second, should it be possible to access (public) endpoints within a "wildcard" project name?
Like, I can currently access my API within the following URLs
Would it be possible to rename the whole thing to something like we can set up ourself?
Maybe there is something and I don't know, so please let me know! Or at least to limit it to _ as it is mentioned in the documentation?
Thank you very much!
Best
Sino
I'm not a 100% sure what you mean, but the first path in the page is the name of the project you're targeting, which enables the ootb multi-tenancy of Directus. Every different name in that first path corresponds to a different project, and therefore a different database.
Most paths of the API, except for the global /server/ ones, are /:project/endpoint
Thats whats written in the documentation and makes absolute sense.
My "problem" is more that all of this routes are right and link to the same project (if there is just one) and so I get always the same result.
BUT shouldn't just one route just work? And all the others are not because there is _no_ project when there is no name like that?
Oh! That doesn't sound right! It should throw an unauthorized error for unknown projects
It should throw an unauthorized error for unknown projects
It is returning the unauthorized error. You can check it in our live demo.
thumper project is created and the below is working too.
https://demo.directus.io/thumper/items/customers?meta=total_count%2Cresult_count&limit=10&access_token=admin
As live demo doesn't contain any project named demo; the below link will throw an error.
https://demo.directus.io/demo/items/customers?meta=total_count%2Cresult_count&limit=10&access_token=admin
As mentioned by @bjgajjar We are getting Unauthorized request exception if project is not setup.
@SinoBoeckmann Can you please confirm with the latest codebase?
Closing this issue due to inactivity. Feel free to reopen. 馃檪