Decoupled route support

Created on 14 December 2023, 7 months ago

Updated 15 December 2023, 7 months ago

Problem/Motivation

The Domain path doesn't support the Decoupled router module → . This provides issues when domain path aliases are created/updated/removed, but the caches for the decoupled route aren't invalidated.

Steps to reproduce

Install and configure the domain path.
Install and configure the decoupled router.
Send a GET request on a path that has not been created yet, say /dummy-path. So, url for GET is /jsonapi/router/translate-path?path=/dummy-path. You get error 404.
Create a node with a domain path /dummy-path.
Send the same GET request as in step 3(GET is /jsonapi/router/translate-path?path=/dummy-path). You get the same error 404

Proposed resolution

I believe this can be solved by cache invalidation on CRUD operations for the domain path entity.

✨ Feature request

Status

Needs review

Version

1.0

Component

Code

Created by

🇺🇦Ukraine _tarik_ Lutsk

Live updates comments and jobs are added and updated live.

Merge Requests

!22Decoupled route support
Open
🇺🇦Ukraine _tarik_
updated 7 months ago

Comments & Activities

Issue created by @_tarik_
Comment 7 months ago →
🇺🇦Ukraine _tarik_ Lutsk
Comment 7 months ago →
🇺🇦Ukraine _tarik_ Lutsk
_tarik_ → changed the visibility of the branch 3408925-decoupled-route-support to hidden.
Comment 7 months ago →
🇺🇦Ukraine _tarik_ Lutsk
_tarik_ → changed the visibility of the branch 3408925-decoupled-route-support to active.
Merge request !22Issue #3408925: Added insert/update/delete hooks for domain path entity to... → (Open) created by _tarik_
Issue was unassigned.
Status changed to Needs review 7 months ago12:15am 15 December 2023
Comment 7 months ago →
🇺🇦Ukraine _tarik_ Lutsk
Changes ready for review.

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024