I was reading the docs - specifically the topic “documentation/topic/seed.c3doc” structure of the seed directory, but it seems to be lacking detail. So we have the standard [seed,src,test] folders, what I’m interested in is what is required/allowed within the seed directory so that an existing type has instances created from seed data. We are using json files with 1:M entries per type to be created during provision.
- Subdirectory - what is required vs allowed for naming, paths, nested folders? I’d like to structure the seed directory just like the source, whereas today our seed directory is flattened.
- json file name - what is required vs allowed for naming of the files? How many seed data files can exist for the same type? Do certain naming of the seed files cause short circuiting of processing other seed files that have the same type content? (ie. seed/TypeA/ folder has 1.json, 2.json, TypeA.json files within it)