The serializer would return an invalid format for the image.ppoi field
causing errors on save through the API even if the API consumer didn’t
modify the ppoi field value.

Apart from that the current implementation caused an internal server
error instead of rejecting invalid formats on save.

Any frontend will need the dimensions of the supplied thumbnails
to select the appropriate thumbnail in different rendering contexts.

Apart from that the thumbnail name is not that helpful, as we need
the full thumbnail URL to be able to display it.

Refactor Note REST API endpoint

See merge request !25

This is mainly so we can start phasing out nested routes.
With nested routes objects were filtered based on route parameters.
Therefore we need something similar in the form of query parameters.

Konrad Mohrfeldt authored 1 year ago and Ernesto Rico Schmidt committed 1 year ago

The image attributes on our models were using VersatileImageField before
our migration to a separate image model. VersatileImageField uses a
VARCHAR field internally that cannot be converted to a ForeignKey.

Signed-off-by: Ernesto Rico Schmidt <ernesto@helsinki.at>

- remove ThumbnailsMixin and thumbnails fields,
- remove image_* fields and theis usage,
- use utils.delete_links function

Replace ModelWithImageFields with foreign key to Image.

- remove ThumbnailsMixin and thumbnails fields,
- remove image_* fields and theis usage,
- use utils.delete_links function

Replace ModelWithImageFields with foreign key to Image.

- remove ThumbnailsMixin and thumbnails fields,
- remove image_* fields and theis usage,
- introduce utils.delete_links function

Replace ModelWithImageFields with foreign key to Image.

Closes: aura#164

Since this may lead to errors while initialazing the container.

Closes: #163

Closes #139

Closes #142