alexdevmotion / strapi-faker Goto Github PK

In the Strapi admin dashboard, it would be super convenient if this plugins' view would be contain some basic features.

Currently, when visiting /admin/plugins/strapi-faker, there's just a blank screen.

As a starting point, maybe the structure like this:

Left sidebar has a list of models.

When clicking a model, right-side data view populates with standard records list (paged) of fake records for the model.

Toolbar at top of right-side view allows to control records, ie delete them all, generate X more, etc.

In the future: To be able to manually set the faker configuration, per-field, for each model.

When I run strapi-faker, it doesn't seem to generate selections for relationship fields.

For example, given models: event, location, user

When I run faker, all the plain fields get fake data. However, relationships like many-users-in-one-event remain blank.

All that needs to be done is a random selection (of id) made of the relationship model; no faker universal data needed.

It would be nice if this could be run on specific models (instead of all models)

For example:
strapi-faker/up/myModel
strapi-faker/down/myModel

It would be nice if fake records were directly and explicitly marked, as opposed to tracking them in an external file, so that at any point of time you can discriminate between fake records and real records.

Why:
1 - To not have to worry about 'up' and 'down' faker states; less worry of corruption
2 - For a richer app development situation, where there's a mix of faker data AND human inputted data, and to be able to discriminate between either at any time
3 - To be able to dynamically toggle fake data on/off downstream (e.g. in the app front-end)

Perhaps a system as such:

For any model which would have fake data generated, a column is deemed to be exclusively used to just track faker state. Perhaps strapi-faker generates this column ("faker_state") ?

When fake records are generated, they get a specific flag in this column (like "1"), marking it as fake.

Now, management and access of fake records is easy as just filtering for the faker flag.

Yes, this changes model structure, but during app development, model structures are changing anyways. Anyone using a faker plugin is presumably pre-production.