Closed (fixed)
Project:
Barcodes
Version:
2.0.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Aug 2023 at 20:08 UTC
Updated:
18 Feb 2024 at 19:34 UTC
Jump to comment: Most recent
Show commands
changes
Comments
Comment #3
tijsdeboeckI've added support for uuid field_type in the barcode field formatter. It is working for our use-case.
Quick tip: Since uuid doesn't have a default formatter at the moment, we found the uuid_extra module very useful. It adds a regular formatter for UUID, so you can easily output the UUID as a regular uuid string, or as a barcode when using both modules.
Comment #4
tijsdeboeckComment #5
tr commentedThanks for the contribution.
In #3353094-3: Support additional field types I said that continually adding new field types is not really scalable, but the Uuid field is part of core, so perhaps we should at least support all the core fields that we can.
Since Uuid is a subtype of a String field, and since we specify that this works for String fields, shouldn't core allow it to be used on Uuid fields? Uuid "is a" String. If the Barcode formatter can handle general unconstrained Strings, it can certainly handle subsets of the String type like Uuid.
Other String field types in core are 'string_long', 'uri', and 'password'
Comment #6
tijsdeboeckHi TR, I understand that core should support this, but it doesn't at the moment (in views at least), see #3112256.
Since it is very simple, doesn't create any issues for this module, and uuid comes with core, I thought it would be a good idea to add support here (at least until core supports it).
Comment #9
sanduhrs