You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each constraints in Symfony have an unique code (uuid, for machine reading).
But those codes are not "documented". I mean, there are no pages on symfony.com which
list all theses code and there associated error.
Why may wonder why we need that. Actually I'm working on an API, and I had to manually document each code :/ I would be nice to document it just once (on symfony.com).
I'm not sure how to build this documentation page
manually in a .rst file
automatically with a parser
The text was updated successfully, but these errors were encountered:
There are literally hundreds of constraints like that ... and that's the only available information: constant name + UUID value.
If you are asking us to document this manually ... that's impossible for us. We have lots and lots of pending features to document, lots of existing articles to review, etc. We don't have time for this, I'm sorry.
If you are asking us to document this automatically ... as you can see, there's no information about the errors. With an automatic parser we can do something like this: a2ad9231-e827-485f-8a1e-ef4d9a6d5c2e = "Not numeric error" ... that's too similar to the constant name.
So, maybe, instead we need some utility in the Symfony code to get the constant name of the given UUID. Maybe there's already something like that?
In any case, I hope you understand this decision 🙏
Hello.
Each constraints in Symfony have an unique code (uuid, for machine reading).
But those codes are not "documented". I mean, there are no pages on symfony.com which
list all theses code and there associated error.
Is has already been suggested here and here
Why may wonder why we need that. Actually I'm working on an API, and I had to manually document each code :/ I would be nice to document it just once (on symfony.com).
I'm not sure how to build this documentation page
The text was updated successfully, but these errors were encountered: