Duplicate "dashboards" entry

[rafalkrupinski]

openapi/openapi/index.yaml

Line 44 in bf60850

"/dashboards":

  "/dashboards":
    $ref: paths/dashboards/index.yaml
  "/dashboards‎":
    $ref: paths/dashboards/singular/index.yaml

[linear]

EDU-501

[rafalkrupinski]

openapi/openapi/index.yaml

Line 68 in bf60850

"/flows":

openapi/openapi/index.yaml

Line 76 in bf60850

"/folders":

didn't check further

[kheiner]

I think this is not actually duplicated, but only appears to be duplicated. See my thoughts in PR #63 related to %E2%80%8E.

When looking at the actual page: https://directus.io/docs/api/dashboards#create-a-dashboard it renders as expected.

You have to configure your editor to show characters that read RTL explicitly rather than render them. In my investigating this, the behavior is by design so that the OpenAPI Spec can interpret the path as unique in it's presentation for the docs.

[rafalkrupinski]

I don't suppose directus handles request at paths ending with that marker? it makes the openAPI doc useless for generating clients or, making calls from OpenAPI renderers like Swagger UI

[kheiner]

I had no knowledge of the hidden character until last night; It appears to work fine in the docs presented by the Directus API endpoint but I don't have any projects to test against whether or not it creates a problem somewhere else.

I do imagine that it might create an issue just from testing this URL https://sandbox.directus.io/collections%E2%80%8E/redirects as I'm assuming it would be constructed by a client

I think #23 is also highlighting this, can you glance there and see if what you're saying is aligning with the concern documented there?

upon closer inspection it's not related.

How are you encountering the problem and/or how did you find this? It appears to me that this is a strange quirk of the Directus API documentation that shouldn't have an impact on users, but if that were the case I don't see how you found it so I must be wrong.

[rafalkrupinski]

Tried generating a python client with python-lapidary but the Directus' OpenAPI is useless as a contract. No problem tho, we're already phasing Directus out.

[kheiner]

Got it; this repository isn't used in any Directus instance; so I don't think the code you've highlighted is causing your issue.

This PR in the directus/directus mono-repo fixes the problem you're calling attention to. It hasn't been merged but you can follow the discussion there to see if it can be.

---

A side note: almost all of the contributions made to open source projects are done by people voluntarily. It's much easier to help people who provide clear examples of the issue they have and maintain a positive, forward-looking posture.