base on Laravel Schedule Calendar - a package providing developers with a concise and visual representation of scheduled tasks, enabling easy analysis of load distribution throughout the day or week for optimized task scheduling. # Laravel Schedule Calendar [](https://packagist.org/packages/indeev/laravel-schedule-calendar) [](https://packagist.org/packages/indeev/laravel-schedule-calendar) [](https://packagist.org/packages/indeev/laravel-rapid-db-anonymizer) [](https://packagist.org/packages/indeev/laravel-schedule-calendar)  ## Overview The Schedule Calendar command has been introduced to provide developers with a clear and insightful view of scheduled tasks within the Laravel application. This new functionality allows for a visual representation of task distribution throughout the day and week, offering a valuable perspective on load distribution. ## Requirements - PHP 7.3 or higher - Laravel 8+ ## Key Features - **Day and Week View:** Easily switch between day and week views to analyze scheduled tasks over different time frames. - **Load Distribution:** Gain insights into the distribution of scheduled tasks throughout the day, helping identify peak load periods and optimize task scheduling. - **Enhanced Debugging:** Use the calendar view as a debugging tool to identify potential conflicts or overlaps in scheduled tasks. ## Installation The Schedule Calendar command is available as a package on [Packagist](https://packagist.org/packages/indeev/laravel-schedule-calendar) and can be installed using [Composer](https://getcomposer.org/). ```bash composer require indeev/laravel-schedule-calendar ``` ## How to Use To leverage the power of Schedule Calendar, simply run the command in your Laravel application: ```bash php artisan schedule:calendar ``` This will generate a visual representation of your scheduled tasks, providing a comprehensive overview of your application's task schedule.  ## Display Option: `--display=dot` The `--display=dot` option provides a visual representation of your scheduled tasks using dots, offering a clear and concise overview. Each dot represents all scheduled tasks in time piece, making it easy to identify the distribution of tasks throughout the specified time range. ### Usage: ```bash php artisan schedule:calendar --display=dot ```  ## Display Option: `--display=list` The `--display=list` option provides a detailed list of concrete commands for each time piece, offering a comprehensive view of your scheduled activities. ### Usage: ```bash php artisan schedule:calendar --display=list ```  ## Range Option: `--range=week` The `--range=week` option allows you to view scheduled tasks for the week around a specified day (or current day as default), providing a broader context of your upcoming activities. ### Usage: ```bash php artisan schedule:calendar --range=week ```  ## Date Selection Option: `--day=YYYY-MM-DD` The `--day=YYYY-MM-DD` option allows you to specify a particular date for viewing the scheduled tasks, providing detailed insights into the tasks for that specific day. ### Usage: ```bash php artisan schedule:calendar --day=yyyy-mm-dd ```  ## Hours per line Option: `--hoursPerLine` The `--hoursPerLine` option allows you to specify how many hours will be displayed per one output line. This parameter provides flexibility in tailoring the visual representation based on your preferences. ### Usage: ```bash php artisan schedule:calendar --hoursPerLine=6 ```  ```bash php artisan schedule:calendar --hoursPerLine=24 ```  ## Contribution 👋 Thank you for considering contributing to our project! We welcome contributions from the community to help make this project even better. Whether you're fixing a bug, improving documentation, or adding a new feature, your efforts are highly appreciated and will be credited. ## Credits - [Petr Kateřiňák](https://github.com/indeev) - [Jarand](https://github.com/lokeland) ## License The MIT License (MIT). Please see [License File](LICENSE.md) for more information. ", Assign "at most 3 tags" to the expected json: {"id":"6169","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"