API: /docs/{docId}/move may move to a WS of a different org #369
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fflorent
changed the title
✅ Deploy Preview for grist-help-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
fflorent
changed the title
fflorent
force-pushed
the
fix-move-doc-endpoint
branch
from
f750288
to
4866d15
Compare
paulfitz
approved these changes
Jul 31, 2024
fflorent
force-pushed
the
fix-move-doc-endpoint
branch
from
4866d15
to
4bda65e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
While looking at the API documentation, I read that the
PATCH /docs/{docId}/moveendpoint specifies that the doc may move to a workspace at the condition that it remains in the same org.We would like to use this endpoint to move the document of an old account's personal org to a new account's one.
After having taken a look at the code and experimented, it looks like it is not the case.
Proposed solution
I simply remove the mention indicating that the target workspace should be in the same org as the source.