Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Purge old url if entity property is change #30

Open
jstuhli opened this issue Sep 9, 2021 · 0 comments
Open

Purge old url if entity property is change #30

jstuhli opened this issue Sep 9, 2021 · 0 comments

Comments

@jstuhli
Copy link
Collaborator

jstuhli commented Sep 9, 2021

Describe the bug
If the property being changed is in the url then we must purge both urls.

Eg.

Lets say we have Post and Tag entities. For simplicity lets say that Post has a single Tag ManyToOne relation.
if we have an endpoint /tag/{name}/posts and we purge on Tag.name change then (currently) only the new {name} will be purged but the old one won't and it will contain stale data.
Same is true if the Post changes it's Tag.

If the changeset of the entity contains the url parameter that needs to be purged, library should queue 2 urls instead of one. If there are multiple parameteres then a cartesian product of all the parameters should be queued.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant