TryGhost
OSS
Ghost
Added router-filter scalar columns to lazy URL field requirements ref https://linear.app/ghost/issue/HKG-1875 A filtered collection router such as featured:true also needs its filter's own columns on the resource to choose the same router eager would. These were neither reported by getRequiredFields nor required on the forward path, so under ?fields=url a thin record let filterMatches see an undefined field and a featured post routed to /:slug/ instead of /featured/:slug/. The non-relation scalar fields a router filter references are now reported so the serializers force them, and required on the forward path so a thin resource is rejected rather than silently mis-routed. Field names are matched only at NQL expression boundaries, so colon-bearing values such as URLs or timestamps are not mistaken for fields; relation fields and the page/type discriminator stay excluded.
nx run ghost:test:legacy
Sign in / Sign up
Open main menu
Succeeded
CI Pipeline Execution
nx run ghost:test:legacy
Click to copy
Linux
4 CPU cores
490b1695
28890