1
0
Fork 0
mirror of https://github.com/archtechx/laravel-tips.git synced 2025-12-12 05:14:04 +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

11 lines
No EOL
493 B
Markdown

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