Replies: 1 comment 1 reply
-
You shouldn't need to. The
There's not - since you can define Runway routes with Antlers, Runway needs to save them in the database in order for them to be queried later. If you don't want them saved in the database, you could disable Runway's routing functionality and define your own routes in
The For example: it could be used to only return models assigned to the logged in user or override the ordering of a model. Those aren't things you'd necessarily want to take affect elsewhere, like in the However, if it'd be useful for you, I would accept a PR that adds another query scope just for the |
Beta Was this translation helpful? Give feedback.
-
Description
I am currently using runway as a read only interface for my resources. The resources I am using are a subest of all my laravel models. I was intially using global scopes to define these but have since used the
scopeRunwayListing
. This has led me to a few questions.runway:rebuild-uris
to capture the new items?runway:rebuild-uris
I think it is generating a uri for all models in the database. Would it be helpful if I submitted a PR to limit this using thescopeRunwayListing
like it does in control panel?Environment
Environment
Application Name: Ripm_Jazz
Laravel Version: 10.45.0
PHP Version: 8.2.15
Composer Version: 2.6.6
Environment: local
Debug Mode: ENABLED
URL: ripmjazz.test
Maintenance Mode: OFF
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: redis
Database: mysql
Logs: stack / single
Mail: smtp
Queue: sync
Session: file
Statamic
Addons: 2
Antlers: runtime
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 4.49.0 PRO
Statamic Addons
jacksleight/statamic-bard-texstyle: 3.1.6
statamic-rad-pack/runway: 6.2.1
Beta Was this translation helpful? Give feedback.
All reactions