Widget to dynamically supply a UID

[pensivedog]

As described here, "relations should not be being declared based on properties that can be edited by a user."

Here's one solution, available as an add in.

IMHO, this is one of the REALLY basic things that any CMS needs in order to be a viable solution for sites with more than a few pages/relations.

[KaneFreeman]

Sounds like a good idea to add.

[robigan]

I have taken an interest in this repo while my PR in the bitcoin repo gets finalized so I might be able to do a PR before v1 drops

[Greenheart]

Would this be helpful as inspiration? I've worked around this by using a custom widget for ids.

uniqueId widget: https://github.com/Greenheart/idg.tools/blob/092ff00f02ca53a8f1910945929619169f53e51a/cms/src/widgets/UniqueId.tsx

Example usage: https://github.com/Greenheart/idg.tools/blob/092ff00f02ca53a8f1910945929619169f53e51a/cms/src/fields/shared.ts#L13

[shumiyao]

I did a similar effort

https://gist.github.com/shumiyao/0d11a37dcfb7e53d97bba8cceaef5b7b

It apparently seems to work.

[KaneFreeman]

This will be part of the 2.0.0 release. Which hopefully will be out in the next few days.

[liufuyang]

@KaneFreeman It would be super nice if we could add a prefix parameter for the UUID widget, so the generated id can be customized such as books/05597998-ab63-4a69-abb6-259846fa4933 when an optional prefix is set to books/.

Do you think it is something easy to add? :)

Just some background info - we are trying to follow Google's "API Improvement Proposals" or AIP - it specifies the "resource names" should be like

Resource name components should usually alternate between collection identifiers (example: publishers, books, users) and resource IDs (example: 123, les-miserables, vhugo1802).

See more here:
https://google.aip.dev/122

If this can be achieved, then the data generated or stored with StaticJsCMS then can be directly loaded into our backend services and we can use the id of each element here as the resource names :)