shivanshs9 opened a new issue #10788:
URL: https://github.com/apache/airflow/issues/10788


   <!--
   
   Welcome to Apache Airflow!  For a smooth issue process, try to answer the 
following questions.
   Don't worry if they're not all applicable; just try to include what you can 
:-)
   
   If you need to include code snippets or logs, please put them in fenced code
   blocks.  If they're super-long, please use the details tag like
   <details><summary>super-long log</summary> lots of stuff </details>
   
   Please delete these comment blocks before submitting the issue.
   
   -->
   
   **Description**
   
   <!-- A short description of your feature -->
   This feature requests a way to support custom views in plugins without any 
menu. Right now, all the views listed in `AirflowPlugin.appbuilder_views` are 
added with menu to the appbuilder.
   
   **Use case / motivation**
   In a custom plugin I built, I need to add a distinct view for details of 
custom operator. Then I use the `BaseOperator.operator_extra_links` to link 
this new UI view with the task links.
   However, this view has no need to show in the airflow menu, but rather 
should be shown in UI similarly to `views.DagModelView`. That is, the view 
should be added to flask appbuilder using `appbuilder.add_view_no_menu` call 
but right now all the views in `AirflowPlugin.appbuilder_views` are added by 
calling `appbuilder.add_view`
   
   **What do you want to happen?**
   
   <!-- What do you want to happen?
   
   Rather than telling us how you might implement this solution, try to take a
   step back and describe what you are trying to achieve.
   
   -->
   
   Maybe if "name" is missing in the dict in `AirflowPlugin.appbuilder_views` 
list, then when integrating plugin to flask app context, it'll just call:
   ```python
   appbuilder.add_view_no_menu(v["view"])
   ```
   otherwise the default behavior.
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to