-
Notifications
You must be signed in to change notification settings - Fork 558
feat(odsp-client): Add etag file conversion API attach options #25804
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -77,6 +77,18 @@ export interface OdspContainerAttachProps { | |
| * The file name of the Fluid file. If undefined, the file is named with a GUID. | ||
| */ | ||
| fileName: string | undefined; | ||
|
|
||
| /** | ||
| * The ID of the item (file) to which the container is being attached. | ||
| * When combined with eTag, this will trigger a conversion of an existing file to a Fluid file. | ||
| */ | ||
| itemId?: string; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: we should probably type these with |
||
|
|
||
| /** | ||
| * Optional eTag to use when attaching the container. | ||
| * If provided, the container will | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Incomplete sentence here, FYI |
||
| */ | ||
| eTag?: string; | ||
| } | ||
|
|
||
| /** | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How coupled are
itemIdandeTag? Would it make sense to combine them into a single object property? Or are they really independent?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The feature only works with both, so I can couple them; however, their the same "level" of metadata as the other properties here, so it would be a bit weird to nest them I think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, do these correspond to external ODSP properties or something? If so, should we document that here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this is information from the external (not-fluid) ODSP file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there public docs we can point to from the interface-level comment? Might be nice to make that relationship explicit in the docs.