# |
Apr 12th 2019, 16:11 |
slackebot |
<abdualelah.mdy> |
# |
Apr 12th 2019, 16:11 |
abdualelah.mdy |
i am using restApi plugin |
# |
Apr 12th 2019, 16:10 |
abdualelah.mdy |
hello |
# |
Apr 12th 2019, 15:48 |
rogerpro |
I wonder if there’s a way for Xdebug to stop at any line of a specific file (apart from excluding all files but this one) — is there a more dynamic way to achieve that? |
# |
Apr 12th 2019, 15:24 |
ricksaccous |
np |
# |
Apr 12th 2019, 15:24 |
louisviart |
Ok, thank's for your help :slightly_smiling_face: |
# |
Apr 12th 2019, 15:22 |
ricksaccous |
nesting doesn't change the limited context |
# |
Apr 12th 2019, 15:21 |
ricksaccous |
probably passing information to validators would be easier |
# |
Apr 12th 2019, 15:20 |
louisviart |
Do you speak about this https://book.cakephp.org/3.0/en/core-libraries/validation.html#nesting-validators ? |
# |
Apr 12th 2019, 15:18 |
ricksaccous |
that way you can get the error to display where you want |
# |
Apr 12th 2019, 15:18 |
ricksaccous |
so maybe just do that |
# |
Apr 12th 2019, 15:18 |
ricksaccous |
before you patch |
# |
Apr 12th 2019, 15:18 |
ricksaccous |
or pass options to a validator |
# |
Apr 12th 2019, 15:18 |
ricksaccous |
also you can technically pass a context to a validator |
# |
Apr 12th 2019, 15:17 |
ricksaccous |
hmmmm |
# |
Apr 12th 2019, 15:17 |
ricksaccous |
what you might want is nested validation |
# |
Apr 12th 2019, 15:16 |
slackebot |
display on the users_information.X I have tried to add this rule in the UserInformations table but I don't have access in the context to the parent table Users ... |
# |
Apr 12th 2019, 15:16 |
louisviart |
I'm trying to solve a problem but I don't know if I'm doing great. I have a User entity wich has one UserInformations that contains a field X This field is in my add / edit form of a user. I would like to perform, conditional validation (https://book.cakephp.org/3.0/en/core-libraries/validation.html#conditional-validation) The problem is that the condition is on the value of the `role` field of the user entity and the message should |
# |
Apr 12th 2019, 15:01 |
ricksaccous |
hello |
# |
Apr 12th 2019, 14:56 |
louisviart |
Hello everyone |
# |
Apr 12th 2019, 14:56 |
josbeir |
yeah as your solution would give a php notice if the key doesn't exist |
# |
Apr 12th 2019, 14:54 |
neon1024 |
Hash is a good shout though @josbeir :ok_hand: |
# |
Apr 12th 2019, 14:54 |
slackebot |
<neon1024> |
# |
Apr 12th 2019, 14:54 |
neon1024 |
Yeah, I went similar |
# |
Apr 12th 2019, 14:45 |
josbeir |
@neon1024 $this->assertArrayHasKey('call.features', Hash::flatten(json_decode('{ "call": { "features": "" } }'))); :rolling_on_the_floor_laughing: |
# |
Apr 12th 2019, 14:43 |
ricksaccous |
too bad we don't account for it in our budgets though |
# |
Apr 12th 2019, 14:43 |
ricksaccous |
hehe |
# |
Apr 12th 2019, 14:43 |
ricksaccous |
as of now the only one who has written a test is me and i just wanted to to be sure some of my logic was correct |
# |
Apr 12th 2019, 14:43 |
ricksaccous |
if i head a project i might make people write some tests |
# |
Apr 12th 2019, 14:42 |
ricksaccous |
hahaha |
# |
Apr 12th 2019, 14:42 |
neon1024 |
Don’t worry, it took me three test suites to figure this stuff out! |
# |
Apr 12th 2019, 14:42 |
neon1024 |
..and if you rebake your fixtures your test -case will fail |
# |
Apr 12th 2019, 14:42 |
ricksaccous |
oh alright |
# |
Apr 12th 2019, 14:42 |
neon1024 |
Which might be out of scope for your test-case |
# |
Apr 12th 2019, 14:41 |
neon1024 |
As you’d be comparing all the keys in the response |
# |
Apr 12th 2019, 14:41 |
neon1024 |
No, you can’t do that either |
# |
Apr 12th 2019, 14:41 |
neon1024 |
You re-bake a fixture with imports, and your test suite will fail |
# |
Apr 12th 2019, 14:41 |
ricksaccous |
lollll |
# |
Apr 12th 2019, 14:41 |
ricksaccous |
you can just do array_keys or something on it and then compare the array of array_keys? |
# |
Apr 12th 2019, 14:41 |
neon1024 |
Asserting values will suffer the same fate |
# |
Apr 12th 2019, 14:41 |
ricksaccous |
oh |