Problem/Motivation
Float, Metatag, URI type fields are not supported by the module. An error is thrown if entity contains a field of unsupported type
Steps to reproduce
Create an entity with field iof type Float / Metatag /URI/ layout_section
Data model changes
Provide proper schema
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | 3304201-16.patch | 1.86 KB | michaelsoetaert |
Comments
Comment #2
gaurav_manerkar commentedComment #3
gaurav_manerkar commentedComment #4
dmitry.korhovLGTM
Comment #5
gaurav_manerkar commentedComment #6
gaurav_manerkar commentedComment #7
gaurav_manerkar commentedAdded support for
layout_sectiontypeComment #8
gaurav_manerkar commentedAdded support for layout_section type
Comment #9
gaurav_manerkar commentedComment #10
gaurav_manerkar commentedComment #11
gaurav_manerkar commentedCreated patch to support URI, Float, layout_section and metatag tyoe.
Comment #12
gaurav_manerkar commentedCreated patch to support URI, Float, layout_section and metatag type.
Comment #13
gaurav_manerkar commentedCreated patch to support URI, Float, layout_section and metatag type.
Comment #14
gaurav_manerkar commentedCreated patch to support URI, Float, layout_section and metatag type.
Comment #15
m.stentaSupport for
floatanduriwere added in #3256795: Decimal and float fields have a null schema and #3390505: Error: uri is not a valid type for a JSON document.Updated title and setting to "Needs work" to refactor accordingly.
If we want to continue with this issue we will need to add automated tests for any new additions (now that #3257911: Add basic test coverage is merged). A merge request would be preferable over patches.
Comment #16
michaelsoetaertUpdated patch of #14 based on comments of #15: Removed code for
float&uri, as these are already supported by the latest version (1.0) of the module.