You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The package looks fantastic and offers great functionality, but I’ve encountered several challenges with the automated installation process:
Dependency on Pending Migrations: If there are pending migrations in the current workspace that rely on country information (e.g., foreign keys or constraints), the package’s migrations must run first. However, the automated process forces all pending migrations to run, which leads to dependency conflicts.
Timestamp Issues: Modifying the timestamps of the package migrations to ensure they run in the correct order can also cause problems and feels error-prone.
Request for Manual Integration Steps
It would be highly beneficial to have a detailed list of steps for manual integration, such as:
Publishing the migrations, configurations, and seeders individually.
Running migrations and seeding commands separately as needed.
This would allow developers to control the integration process more effectively, especially in projects with complex migration dependencies.
Testing Automation Suggestion
For automated testing purposes, it would also be helpful to have a single command to seed the required data without running the entire installation process.
Proposed Benefits:
Greater flexibility and control during package integration.
Avoid migration conflicts in existing projects.
Streamlined workflow for automated testing.
Thank you for your efforts on this package, and I hope these suggestions can enhance its usability and integration process!
Best regards
The text was updated successfully, but these errors were encountered:
First of all, thank you for such a clear and detailed issue! It really means a lot to me to see someone with such great ideas contributing to the package. Your insights will greatly benefit the project and the developers using it! 🚀
I'm keeping this issue open because I'm actively working on a more elegant and flexible installation process, along with an option for a fully manual installation.
I’ll also make sure to thoroughly document every step of the manual installation process, so developers have complete control over it.
I completely understand the concerns regarding timestamps—this was an unintended issue, and I’ll make sure this doesn’t happen again.
I’m currently working on a solution to address this problem, and as soon as I have dedicated time to finalize this update, I’ll provide an update here. Thank you again for your patience and for helping improve the package! 😊
Hi,
The package looks fantastic and offers great functionality, but I’ve encountered several challenges with the automated installation process:
Dependency on Pending Migrations: If there are pending migrations in the current workspace that rely on country information (e.g., foreign keys or constraints), the package’s migrations must run first. However, the automated process forces all pending migrations to run, which leads to dependency conflicts.
Timestamp Issues: Modifying the timestamps of the package migrations to ensure they run in the correct order can also cause problems and feels error-prone.
Request for Manual Integration Steps
It would be highly beneficial to have a detailed list of steps for manual integration, such as:
This would allow developers to control the integration process more effectively, especially in projects with complex migration dependencies.
Testing Automation Suggestion
For automated testing purposes, it would also be helpful to have a single command to seed the required data without running the entire installation process.
Proposed Benefits:
Thank you for your efforts on this package, and I hope these suggestions can enhance its usability and integration process!
Best regards
The text was updated successfully, but these errors were encountered: