optional parameters

[ivang76]

Hi all,
I'm wondering if should be possible to define an optional parameter, within the route field in the collection's yaml file.
For example something like this (usual laravel approach) for a specific param:

title: Pages
sites:
  - de
  - en
propagate: true
template: default
layout: layout
revisions: false
route: 'page/{slug}/{special_id?}'
sort_dir: asc
preview_targets:
  -
    label: Entry
    url: '{permalink}'
    refresh: true
structure:
  root: true

the page goes in 404 if it is not present or if its value is not exactly "spacial_id" (so it is not a dynamic value). why?
I would need to use special_id in a view model to query a model and create some logic to return value at the view...

thanks!

[jasonvarga]

If a value is missing, it'll just be filtered out of the route.

For example if you have a route like this: page/{slug}/{special_id}
And an entry with a special_id, its url would be: page/my-slug/my-special-id
An entry without a special it, its url would be page/my-slug

Is special_id a real field or are you defining it in the view model?

[ivang76]

thanks for the prompt reply

it is not a real field, it is just a value that I have to pass via url and that I'll need to use in the view model.
So for example I would like to manage routes like these:
https://www.siteunderconstruction.com/slug-of-something/3455
or
https://www.siteunderconstruction.com/slug-of-something

and then I would use the 3455 (in the view model, like I would do in a normal laravel controller via normal laravel routing) to query a model and get a records (for example) to do something specific to be returned to a view.

How should I define these cases with the route param in the yaml file of a collection?

[ivang76]

Ah, I see. Okay, I understand now. So, the only viable approach seems to be following the standard Laravel flow with routes and controllers. However, this would mean sacrificing the management of Statamic pages in the control panel, which is unfortunate.

I've also noticed that introducing an additional mandatory parameter for special reasons might not be straightforward. For instance, the following route works:
'page/{slug}/{id}'
where 'id' is the identifier found in the Markdown page.

Instead, something like this doesn't seem to work as expected:
'page/{slug}/{some_param_that_I_wanna_create}'

Am I correct in understanding this, or is there something I might be overlooking? Thanks again!

[jasonvarga]

You can create a separate route yourself that loads the entry.

Route::get('page/{slug}/{special_id?}', function ($slug, $specialId = null) {
  $entry = Entry::query()->where('collection', 'whatever')->where('slug', $slug)->first();
  $entry->setSupplement('special_id', $specialId);
  return $entry;
});

[ivang76]

does this mean that I'll get the 'special_id' in the view model linked to the page?

[jasonvarga]

It'll be available as {{ special_id }} in your templates.

[ivang76]

ok thanks