Add wildcard urls - a proposal

[kulturbande]

What is this pull request for?

Add a possibility to create wildcard pages. A page layout can now have a wildcard_url (e.g. ":awesome_id"). With that in place it is possible to create dynamic pages.
This PR is only the technical groundwork. It does not handle admin view changes. It would be preferable to prevent changing the slug in the page information modal and it would be helpful for the user to see a hint in the page tree, if a page contains wildcards.

Screenshots

Page Layout Configuration

A resolved URL

View Template

Page Sitemap

Page Properties

Checklist

• I have followed Pull Request guidelines
• I have added a detailed description into each commit message
• I have added tests to cover this change

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.08%. Comparing base (d187dd2) to head (cee199b).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3776      +/-   ##
==========================================
+ Coverage   98.06%   98.08%   +0.02%     
==========================================
  Files         322      324       +2     
  Lines        8526     8635     +109     
==========================================
+ Hits         8361     8470     +109     
  Misses        165      165              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kulturbande]

I adjusted the whole structure on this PR and updated the page defintion to use wildcard_url as parameter.

[kulturbande]

I renamed the service to page_finder and the signature is way leaner.

[tvdeyen]

Two suggestions for PageFinder:

---

Single-query optimization for find_by_wildcard_url

Instead of walking the tree level by level (one query per depth level), we could avoid the N+1 with a single query approach:

1. Try exact match first (already done, single query)
2. If no match, load all pages whose urlname contains wildcard markers in one query:

candidates = Current.language.pages.contentpages.where("urlname LIKE ?", "%:%")

3. Then match in Ruby:

input_segments = urlname.split("/")  # ["products", "42", "comments"]

candidates.find do |candidate|
  pattern_segments = candidate.urlname.split("/")  # ["products", ":id", "comments"]
  next unless input_segments.size == pattern_segments.size

  # match static segments exactly, extract params from wildcard segments
end

Since urlnames are stored with wildcard patterns literally (e.g., products/:id/comments), this works without tree traversal. The set of wildcard-path pages should be small.

For ambiguous matches (multiple candidates with same segment count), we'd need explicit priority — e.g., prefer the most specific match (most static segments). But that's solvable.

---

Validate constraint types in WildcardUrlType

Currently matches_constraint? silently passes when a constraint type is unknown (e.g., a typo like integre instead of integer). This should be caught early — WildcardUrlType#assert_valid_value could validate that each param constraint references a known format matcher:

if value.is_a?(Hash) && value[:params].is_a?(Hash)
  value[:params].each_value do |constraint|
    next unless constraint.is_a?(String)
    unless Alchemy.config.format_matchers.respond_to?(constraint.to_sym)
      raise ArgumentError, "Unknown format matcher: #{constraint.inspect}"
    end
  end
end

That way typos blow up at YAML load time, not silently at request time.

[tvdeyen]

I would prefer to handle this in url_path instead.