[NXDRIVE-2027] Allow Direct Edit on custom blob metadata values - Nuxeo Issue Tracker

XML

Word

Printable

Release Notes Summary:
Direct Edit and custom blob metadata values
Release Notes Description:
Hide

Direct Edit can now handle any custom blob metadata; there are no more limitations on the xpath.

Those are all valid (given "s" for string and "n" for number):

s:s (file:content, foo:bar, note:note)

s:s/n (files:files/0, foo:bar/0)

s:s/n/s (files:files/0/file)

s:s/n/n/n/n/s/n/s:s... (foo:baz/0/0/0/0/file/0/real:file...)

Notes handling is stricter, only note:note is taken into account, nothing changed.
Show
Direct Edit can now handle any custom blob metadata; there are no more limitations on the xpath . Those are all valid (given "s" for string and "n" for number): s:s ( file:content , foo:bar, note:note) s:s/n (files:files/0, foo:bar/0) s:s/n/s (files:files/0/file) s:s/n/n/n/n/s/n/s:s.. . (foo:baz/0/0/0/0/file/0/real:file...) Notes handling is stricter, only note:note is taken into account, nothing changed.
Tags:
Sprint:
nxDrive 11.1.27
Story Points:
1

If one defines a custom blob metadata, let's say foo:bar instead of files:files, then direct Edit will fail on something like:

WARNING  nxdrive.direct_edit No blob associated with xpath 'foo:bar/0' for file '/default-domain/workspaces/folder/file'

A patch has been provided in the linked ticket, let's use it and add a simple test case.

Estimated:

Not Specified

Remaining:

Logged: