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

Replace path API endpoint shouldn't error if the path doesn't exist currently #3361

Closed
bouk opened this issue May 16, 2024 · 0 comments · Fixed by #3362
Closed

Replace path API endpoint shouldn't error if the path doesn't exist currently #3361

bouk opened this issue May 16, 2024 · 0 comments · Fixed by #3362

Comments

@bouk
Copy link
Contributor

bouk commented May 16, 2024

Describe the feature

Currently the replace path endpoint return 404 when setting an endpoint that doesn't exist currently, which doesn't really serve any purpose since the path is replaced anyways. This is annoying for clients, since they have to loop to try creating the path instead which can then also fail, because it might've been created in the meantime.

Making it accept replace for paths that don't exist yet will make it idempotent

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

Successfully merging a pull request may close this issue.

1 participant