- Created a JSON file for the security audit report dated 2026-07-19, detailing various security findings and their relationships.
- Added a JSON file for seed test data, including user creation logic and dependencies in the `seed_testdata.php` file.
- Introduced a JSON file for the AdminCspSubscriberTest, outlining test cases and their structure in the `AdminCspSubscriberTest.php`.
- Created a new JSON file for the insurance API documentation, detailing endpoints, parameters, and responses.
- Added a JSON file for the PurgeDoctorsCommandTest, including test methods and their relationships to the command and other components.
This commit introduces a new JSON file that contains the abstract syntax tree (AST) representation for the migration file Version20260719044321.php. The AST includes nodes for the migration class, its methods, and their relationships, as well as raw calls made within the migration. This structure aids in understanding the code's architecture and dependencies.
- Introduced a new nullable city_id column in the blogs table to allow scoping of blog posts to specific cities.
- Updated Blog entity to include a ManyToOne relationship with the City entity.
- Enhanced BlogController to handle city_id in the request, allowing filtering of posts by city.
- Modified BlogRepository to support querying published posts based on city_id.
- Added tests to ensure correct behavior for city-scoped and nationwide posts, including creation and updating of posts with city associations.
- Created JSON representation for VisitPriceRequirementResolver.php, including nodes and edges for methods and imports.
- Added AST cache for migrations/Version20260717093000.php, detailing methods and their relationships.
- Introduced AST cache for DiscountRuleRepository.php, capturing methods, imports, and their interactions.
- Created a new JSON file containing nodes and edges representing the structure of the insurance API documentation.
- The nodes include various API endpoints, their labels, file types, and source locations.
- The edges define relationships between the nodes, indicating how they are connected within the documentation.