How does the page registration logic (new in SAF-CLI 4.2.0) work?

Lucas Boucinha (snps)

Hi,

I'm upgrading my "solution's template" to be as closed as possible as the one generated with SAF-CLI 4.2.0.

I can see (for example in the <path_to_my_solution>\ui\pages\first_page.py) that pages are now registered using this below dash command:

dash.register_page(
    __name__,
    name="First Step",
    path_template="/projects/<project_id>/first-step",
    icon_asset_name="game-icons--crossed-air-flows.svg",
    icon_asset_path="icons",
)

I understand how this is used in the <path_to_my_solution>\ui\pages\page.py module to automatically discover the solution's pages, using the get_page_list(..) helper and render them with the render_nav_tree, display_page and open_new_page (newly added) callbacks.

But I'd like to better understand how the path_template="/projects/<project_id>/first-step" argument must be setup at registration call.

In particular what is the "first-step" part of the given string? Can't it be identified automatically?

Can you please share a link if that is documented somewhere?

Thanks once more for your help!

BR/L.