nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

BUG - GET REST API returns strings for non-string primitives

russtrotter_ · 2013-11-26T17:41:11+00:00

Here's the setup: * In Nuxeo Studio, create new Document Type "mydoc" * On Schema tab, add a field "foo" type "Boolean" * Save * In DM, update project from studio * Create a new "mydoc" in Document Management * Call REST API /nuxeo/api/v1/path/default-domain/workspaces/myworkspace/mydoc * In returned JSON, the field "foo"…

russtrotter_

Here's the setup:

In Nuxeo Studio, create new Document Type "mydoc"
On Schema tab, add a field "foo" type "Boolean"
Save
In DM, update project from studio
Create a new "mydoc" in Document Management
Call REST API /nuxeo/api/v1/path/default-domain/workspaces/myworkspace/mydoc
In returned JSON, the field "foo" is returned as "true" or "false" (with the quotes)

By comparison, POSTing to the same API allows a JSON boolean to be posted. It would seem to be most useful if the GET API worked the same way.

When I get some time I'll go through the Nuxeo DM code and find the spot where this is ocurring and post follow-up comment on this question.

Find more posts tagged with

Comments

russtrotter_

Dug through the nuxeo-features code base and found