docs: add schedule_id as a parameter for schedule in LabelScheduleSource usage example

Author: danfimov

docs/available-components/schedule-sources.md

@@ -34,12 +34,13 @@ The format of the schedule label is the following:
 @broker.task(
     schedule=[
         {
-            "cron": "* * * * *", # type: str, either cron or time should be specified.
+            "cron": "*/1 * * * *", # type: str, either cron or time should be specified.
             "cron_offset": None # type: str | timedelta | None, can be omitted.
             "time": None  # type: datetime | None, either cron or time should be specified.
             "args": [], # type List[Any] | None, can be omitted.
             "kwargs": {}, # type: Dict[str, Any] | None, can be omitted.
             "labels": {}, # type: Dict[str, Any] | None, can be omitted.
+            "schedule_id": "every_minute",  # type: str | None, can be omitted.
         }
     ]
 )
@@ -55,6 +56,7 @@ Parameters:
 - `args` - args to use, when invoking the task.
 - `kwargs` - key-word arguments to use when invoking the task.
 - `labels` - additional labels to use when invoking the task.
+- `schedule_id` - unique identifier of the schedule. If not specified, a random uuid will be generated.
 
 To enable this source, just add it to the list of sources:
 

docs/extending-taskiq/schedule-sources.md

@@ -12,3 +12,8 @@ Here's a minimal example of a schedule source:
 @[code python](../examples/extending/schedule_source.py)
 
 You can implement a schedule source that write schedules in the database and have delayed tasks in runtime.
+
+::: info Cool tip!
+You can also use `LabelScheduleSource` as a base class for your schedule source
+if you want to parse schedules from task labels and don't want to implement logic for this from scratch.
+:::