Is your feature request related to a problem? Please describe.
Yes. Currently, the project supports SeedFile import functionality only when using MongoDB. However, after the introduction of the in-memory database (memory database) support, the SeedFile import was not implemented for it. This leads to inconsistent behavior and lack of initial data when running with memory database, which especially affects testing and development scenarios.
Describe the solution you'd like
I’d like to implement SeedFile import support for the memory database, so that regardless of whether MongoDB or memory database is used, the application will import seed data consistently from the SeedFile during initialization.
Describe alternatives you've considered
- Manually mocking or inserting data when using memory database (not ideal for large seed sets).
- Skipping tests that depend on seed data when using memory database (not scalable).
- Using MongoDB for all environments (defeats the purpose of having a lightweight in-memory mode for testing/dev).
Additional context
This feature ensures consistency across different database modes and improves the reliability of local development and testing workflows.
I plan to submit a PR to add this functionality.
Is your feature request related to a problem? Please describe.
Yes. Currently, the project supports SeedFile import functionality only when using MongoDB. However, after the introduction of the in-memory database (memory database) support, the SeedFile import was not implemented for it. This leads to inconsistent behavior and lack of initial data when running with memory database, which especially affects testing and development scenarios.
Describe the solution you'd like
I’d like to implement SeedFile import support for the memory database, so that regardless of whether MongoDB or memory database is used, the application will import seed data consistently from the SeedFile during initialization.
Describe alternatives you've considered
Additional context
This feature ensures consistency across different database modes and improves the reliability of local development and testing workflows.
I plan to submit a PR to add this functionality.