Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FormError] Add support for string cause and null cause #24

Open
Nek- opened this issue Aug 1, 2019 · 0 comments
Open

[FormError] Add support for string cause and null cause #24

Nek- opened this issue Aug 1, 2019 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers
Milestone

Comments

@Nek-
Copy link
Contributor

Nek- commented Aug 1, 2019

Currently, the FormErrorResponse does not support null and string causes. It may occur more than we think. This should be added.

The following should be enough:

if ($cause === null) {
    return [$formError->getMessage(), $propertyPath];
}

if (is_string($cause)) {
    return [$cause, $propertyPath];
}
@Nek- Nek- added the good first issue Good for newcomers label Aug 1, 2019
@Nek- Nek- added this to the v0.4.x milestone Aug 10, 2019
@Nek- Nek- added the enhancement New feature or request label Aug 10, 2019
@Nek- Nek- modified the milestones: v0.4.x, v0.6 Apr 2, 2020
Nek- added a commit to Nek-/Melodiia that referenced this issue Nov 26, 2021
…curity

Make security optional in crud controllers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant