Implement updateFileMetadata use case #249
Open
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
ChengShi-1
added
Waiting
SPA.Q1.6
ChengShi-1
force-pushed
the
213-implement-use-case-for-edit-files-metadata-on-file-page
branch
from
02db5f7 to
2353a8f
Compare
…adata-on-file-page
g-saracca
requested changes
Feb 27, 2025
|
@g-saracca Hi German, I finish my updates in this PR, please check it again. Thanks! |
g-saracca
approved these changes
Feb 28, 2025
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.
What this PR does / why we need it:
Inspired from this TODO as well as the 2025 Q1 proposal. The File edit option for single file could be implemented since the api endpoints are ready here.
Which issue(s) this PR closes:
Related Dataverse PRs:
Special notes for your reviewer:
Suggestions on how to test this:
Visually inspect and make sure that tests pass
Is there a release notes update needed for this change?:
Additional documentation: