[
https://issues.apache.org/jira/browse/AIRFLOW-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515054#comment-16515054
]
Ash Berlin-Taylor commented on AIRFLOW-2598:
--------------------------------------------
I'm quite strongly against ReactJS for this project - it adds a whole extra
level of complexity that would make it harder for many members of the community
to contribute - I'd be surprised if many people in the "data" space are
comfortable with ReactJS.
I also have a bug bear about JS-only apps and am very strongly in favour of
progressive enhancement - i.e. most functionality and content should be
available in the initial page load without JS or subsequent requests. Does
React make it easy to do this?
I would start a discussion on this on the mailing list.
If you do start playing around with a port anyway make sure you do it off the
new www ui based on Flask-AppBuilder (which is in master as the alpha/beta
config option. I forget the exact name(
> Migrate Airflow to ReactJS
> --------------------------
>
> Key: AIRFLOW-2598
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2598
> Project: Apache Airflow
> Issue Type: Improvement
> Components: webapp
> Reporter: Verdan Mahmood
> Priority: Major
> Labels: frontend
>
> Hi guys,
> In an effort to make the frontend of Apache Airflow more interactive and
> feature-rich, I am planning to migrate the frontend to ReactJS.
> The whole idea involves adding/updating the backend APIs and redesigning the
> frontend in ReactJS, along with fixing bugs and improving layouts. This issue
> is the starting point to discuss the need, process and timeline to make it
> happen collectively.
> For the next couple of weeks I would be working on backend in order to add
> remaining APIs and make them ready for the frontend use. Question: Do we have
> any kind of documentation or list of existing and outstanding APIs (roadmap)?
> I am hoping to get your input on how to structure the frontend code, so that
> we can deliver more frequently and incrementally in the best possible way. It
> could be a separate repository or a directory within the same repository.
> Thoughts? It would be great if I can also get some feedback on UI/UX, as
> whether to keep it same or do some user research to improve that?
> Note: I'll make sure to keep the backward compatibility in mind all the time
> while doing that :)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
