You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/09/02 18:00:03 UTC
[jira] [Assigned] (AIRFLOW-2616) Pluggable class-based views for
APIs
[ https://issues.apache.org/jira/browse/AIRFLOW-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned AIRFLOW-2616:
-------------------------------------
Assignee: Holden Karau's magical unicorn
> Pluggable class-based views for APIs
> ------------------------------------
>
> Key: AIRFLOW-2616
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2616
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
> Reporter: Verdan Mahmood
> Assignee: Holden Karau's magical unicorn
> Priority: Major
> Labels: api_endpoints, architecture
>
> With the increase of API code base, the current architecture (functional views) will become messy in no time. Same routes with different http methods become more confusing in the code base.
> We can either use Flask's Pluggable views, which are inspired by Django's generic class-based views to make our API structure more modular, or we can look for Flask-RESTful framework.
>
> http://flask.pocoo.org/docs/0.12/views/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)