1
0
Fork 0
mirror of https://github.com/archtechx/laravel-tips.git synced 2025-12-12 21:34:03 +00:00
laravel-tips/content/tips/you-can-use-wherenumber-on-routes-instead-of-passing-a-regex-pattern-to-where.md
lukinovec 1a53831d4d
Weekly thread #5-#7, use actual created_at timestamp in Thread creation (#27)
* Weekly thread #5

* Weekly thread #6 (before #5)

* Weekly thread #5

* Correct the weekly thread created_at timestamps

* Add actual created_at to Thread

* Weekly thread #7

* Fix weekly thread #7

* Remove thread #8
2022-02-21 17:24:21 +01:00

493 B

title tweet_id thread_slug author_username images created_at slug
You can use whereNumber() on routes instead of passing a regex pattern to where() 1495414943612506113 weekly-thread-2022-07 Sileence
https://pbs.twimg.com/media/FLZ9iNEX0AcKQVD.jpg
2022-02-20T15:08:00+00:00 you-can-use-wherenumber-on-routes-instead-of-passing-a-regex-pattern-to-where

I'm reading the Laravel 9 docs from scratch and TIL you can write your route restrictions in a more expressive way: