what is that plugin about? the name is too much generic
This plugin, or rather the two custom fields that it introduces (CustomRelation and CustomEnumeration), is used to solve cases of this type:
It’s true, the name is too generic.
Unfortunately I never took the time to change their name or even to make more complete documentation.
I had to develop this plugin for work, because I needed it for an automotive customer, where I need to select in cascade, the brand then the model among the models associated with the chosen brand and finally the version associated with the chosen model.
Once finished and tested with my customer (still in use) I decided to share it with the community.
The problem is as you say, I gave it a name that was too generic and I haven’t written a decent documentation yet
Luckily I saw from the issues that some people managed to use it
what about rename it?
I started working today to change the name of the plugin. Once finished I will try to write a more complete documentation and publish it on npm.
If anyone is curious and/or wants to contribute I will start making changes on this branch:
Any advice is welcome even from the most banal as it may be, the name to assign to the plugin
I just wrapped up the documentation for the plugin, strapi-plugin-parent-child-relationships, and it’s officially live on npm! You can check it out here:
For those currently using the old version, I’ve included instructions on how to transition to the new plugin: