Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-2027

Allow Direct Edit on custom blob metadata values

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: NoFixVersionApplicable
    • Fix Version/s: 4.4.2
    • Component/s: Direct Edit
    • 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.
    • Sprint:
      nxDrive 11.1.27
    • Story Points:
      1

      Description

      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.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours
                2h

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.