GitLab

--HG--
branch : 0.2

--HG--
branch : 0.2

We do this because CubicWeb 3.29 did breaking changes.

--HG--
branch : 0.2

--HG--
branch : 0.2

--HG--
branch : 0.2

* Since CubicWeb 3.29, GET requests do not respect the application/json mime
  type sent with the Accept header, causing application to retrieve an HTML
  output instead of formatted JSON output
* Using the /jsonschema prefix ensure to retrieve JSON output without break
  any previous behavior

--HG--
branch : 0.2

--HG--
branch : 0.2

--HG--
branch : 0.2

Note: (nspanti) We currently kept compatibility with CubicWeb
3.26 and 3.27, but it is temporary.

--HG--
branch : 0.2

Note: (nspanti) It is grafted from 0.1. We temporally keep
compatibility with old CubicWeb versions (already removed in 0.1).

--HG--
branch : 0.2

Why? Because we don't test anymore with older versions.

--HG--
branch : 0.2

Why? Because we don't test anymore with older versions, that are
dead and it is definitive.

--HG--
branch : 0.2

Note: (nspanti) It is grafted from master branch and usefull not
to have to remember or search how to publish on PyPi.

--HG--
branch : 0.2

Thanks to this, merge with 0.1 branch will be smaller.

--HG--
branch : 0.2

Why? Because we don't test anymore with older versions. Moreover,
even version 2.7 is already dead and should not be used anymore.

--HG--
branch : 0.2

--HG--
branch : 0.2

--HG--
branch : 0.2

The title is not needed for the support of the translation for all the schema entries.

--HG--
branch : 0.2

--HG--
branch : 0.2

--HG--
branch : 0.2

--HG--
branch : 0.2

self.val has been renamed to self.values
(grafted from 0ec8ffbeb8f8)

--HG--
branch : 0.2

--HG--
branch : 0.2

--HG--
branch : 0.2

For unauthenticated users, request.cw_cnx is None.
(grafted from 6375410358c8)

--HG--
branch : 0.2

--HG--
branch : 0.2

--HG--
branch : 0.2

- Add a test for object relations
- Change _relation_mapper signature to accept "role"
- Add a _relations attribute that contains relation/role pairs
- Use the new _relations instead of the old relations attribute
- Hide subject and object relations mapped to this document from etype JSON Schema
- Add 2 tests to detect relation duplications
- Detect relation duplications

--HG--
branch : 0.2

JSON Schema validation of an instance is arguably the responsibility of
the client and it's not very useful to (re-)validate the instance on
server side with a JSON Schema validator since we already have a
validation in the database.

Also, it creates problems with combined usage of "default" and
"required" when the client does not supply a value (which is
legitimate). Closes #17115851. (Added a test for this.)

In ETypeMapper.values(), we now check that "instance" is completely
consumed when all mappers of the graph have been called and if not, we
issue a validation error similar to what a JSON Schema validator would
have raised since we have `"addionnalProperties": "false"` on our JSON
Schema.

There's no behaviour change in tests, just some error messages changes.
Useless tests are dropped.

We do not depend on python-jsonschema anymore in application code, but
only in tests.

--HG--
branch : 0.2

The latter works by using whatever python3 executable points to.

--HG--
branch : 0.2

--HG--
branch : 0.2

--HG--
branch : 0.2

There appears to be no reason to have name unicity amongst
all entity types.

--HG--
branch : 0.2

All subclasses of BaseRelationMapper but AttributeMapper override this method
which behavior is actually only valid for attribute-relation.

This is useful to had PUT requests working with a body containing all required
fields with unmodified values for attributes for which update is not allowed.
Added a test highlighting this.

Implement a "_type" method for DateMapper (which DatetimeMapper inherits from)
that parses the string date as ISO8601 format (similar to what we render in
the HTTP API). Add a dependency on iso8601 package that provides a parser for
this.

In many cases, such errors would occur for an internal reason not because of
an invalid request. So prefer "500 Internal Server Error" over "400 Bad
Request" which might be misleading if the error is actually "internal".

Later on, we should make a proper distinction between true internal errors and
*currently unhandled* client errors. One such case concerns converting
TypeResolverException that might occur when setting a relation to a bad target
into a proper Bad Request (hence the "TODO" in respective test).

As demonstrated in test, this might occur if an exception with no message is
raised (str(exc) == '').