Log message #4208912

# At Username Text
# Oct 15th 2019, 09:11 jotpe In fact, I have this piece of code added to several `$routes->connect`:
# Oct 15th 2019, 09:09 slackebot1 <jotpe>
# Oct 15th 2019, 09:08 jotpe I have a route which is `example.com/konferenzen/2020/einreichen/` I used `Router::plugin` and `$routes->scope()` to simplify my routes a bit:
# Oct 15th 2019, 09:04 neon1024 What’s the use-case?
# Oct 15th 2019, 09:01 jotpe Is there a way to use `setPatterns`/`setPass` for several Routes or a scope?
# Oct 15th 2019, 09:00 jotpe Morning
# Oct 15th 2019, 08:58 neothermic woo
# Oct 15th 2019, 08:57 neothermic I could just put 3.3.16, because you're not going to release another 3.3 line update :P
# Oct 15th 2019, 08:57 dereuromark and it is cleaner in terms of semver than using .* :slightly_smiling_face:
# Oct 15th 2019, 08:57 dereuromark well, still, wrong constraint, `~3.3.0` is the one you needed.
# Oct 15th 2019, 08:57 neothermic I didn't mistake anything, this was using `composer create-project --prefer-dist cakephp/app:3.3`
# Oct 15th 2019, 08:56 dereuromark well, you did the mistake of not setting 3rd digit, then ~ would work fine
# Oct 15th 2019, 08:56 neothermic I had to manually alter the composer.json afterwards to change the `cakephp/cakephp: "~3.3"` line to `cakephp/cakephp: "3.3.*"`
# Oct 15th 2019, 08:55 dereuromark or you use "~5.5.9" etc and see if that works
# Oct 15th 2019, 08:55 dereuromark thats how you properly lock it down: https://github.com/dereuromark/cakephp-sandbox/blob/master/composer.json#L123-L125
# Oct 15th 2019, 08:54 neothermic I suppose it is! hmm
# Oct 15th 2019, 08:53 dereuromark thats all correct?
# Oct 15th 2019, 08:51 neothermic despite the fact that the require line in composer.json has: ``` "require": { "php": ">=5.5.9",```
# Oct 15th 2019, 08:51 neothermic install cakephp/app 3.3, and it installs cakephp 3.8.5 ¬_¬
# Oct 15th 2019, 08:50 neothermic well, that's fun
# Oct 15th 2019, 08:35 dereuromark I never do this anti-pattern for usability for this very same reason.
# Oct 15th 2019, 08:35 dereuromark nope, not properly. Try it out with other messages alongside.
# Oct 15th 2019, 08:11 alexdd55976 morning
# Oct 15th 2019, 07:54 conehead Morning
# Oct 15th 2019, 07:54 spriz I am sure we have "already exists" in our UIs, but we have that only in `buildRules` afaik
# Oct 15th 2019, 07:53 spriz I see :thinking_face: But those errors in the `buildRules` is also shown in the UI - aye?
# Oct 15th 2019, 07:47 neon1024 Morning everyone :wave:
# Oct 15th 2019, 07:47 conehead :P
# Oct 15th 2019, 07:41 ruth.cantoni facade
# Oct 15th 2019, 07:38 dereuromark Pretty sure i once Blogged about this^^
# Oct 15th 2019, 07:37 dereuromark Actually that is how it should be done correctly for usability.
# Oct 15th 2019, 07:37 dereuromark @conehead it might just be the status quo of passing tests :)
# Oct 15th 2019, 07:19 spriz That looks like sorcery usage of `Validator` :O :)
# Oct 15th 2019, 06:22 conehead @tippexs91 I don't get your test case? You expect that the result is empty twice. So actually it never should be saved?
# Oct 14th 2019, 22:00 dereuromark https://github.com/dereuromark/cakephp-sandbox/blob/master/plugins/Sandbox/src/Model/Table/AnimalsTable.php#L49 works perfectly for me
# Oct 14th 2019, 21:58 dereuromark so how did you set up the validation? because usually it works.
# Oct 14th 2019, 21:53 tippexs91 make sense to me, but still the question. How to write a suitable test for isUnique Validations? Would be very cool to have the possibility to test this before releasing the production build.
# Oct 14th 2019, 21:49 challgren This would be a prime example of returning a http 402
# Oct 14th 2019, 21:48 tippexs91 Yeah. In this case we need to deal with a not very stable sub-system sending updates to our payments. Therefore the payment_id need to be unique. If I have a entry for a given payment_id already, i will not save the current one and send a 400.
# Oct 14th 2019, 21:37 dereuromark rules are best for data integrity check, especially if you want to catch db constraints early. but for me isUnique is part of validation and should find its way into meaningful user output.
# Oct 14th 2019, 21:33 tippexs91 okay to be clear... validations are good for sementical checks... but not for checks like that?