pateash edited a comment on pull request #16931:
URL: https://github.com/apache/airflow/pull/16931#issuecomment-883062473
@ashb @potiuk @kaxil @uranusjr @ryanahamilton
Please correct me If I am wrong here,
As far as I know we use DagModel object to render dag information in UI,
so for timeline even if we use something like an Enriched Python Object in
the future, we will still need to store that information in Database/DagModel.
```python
class MyCustomTimetable(Timetable):
...
dag = DAG(
...,
timetable=MyCustomTimetable(),
)
```
So, while rendering in UI, we will need that information in DagModel and we
can't use **DAG.timetable**.
I think, whenever we do a change in DAG Api for allowing **timetable** as an
argument, we can modify our model to accommodate that change and show the
description according to the requirements needed at that point in time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
