fpurcell
commented
5 years ago Another task will be to refactor the code for React 17 (there'll eventually be such a thing: https://github.com/facebook/react/milestone/40) and Hooks, etc... That might also trigger a re-think on the use of redux (I get the impression that's falling out of favor). See https://github.com/opentripplanner/otp-react-redux/issues/47
A future improvement development task to see OTP-RR (and TriMet MOD) library refactored to be more a component library.
In such a refactor, there are two features I'd love to see:
a) more independence between the Components ... for example, maybe I'd like to use the Trip Planner, Stops and/or Route Viewer in a different React map than the map that is used in OTP-RR (e.g., maybe on this map, for example: https://modbeta.trimet.org/vehicles/
b) an extension scheme, where I could extend the functionality of the components w/out having to dig deep into the current code. For example, with the Route Viewer or Stop Popups -- I'd like an easy way to have those components make calls into my Real-time Vehicle layer, such that I could show routes and vehicles together.
Consider this me just talking at this point (e.g., not actionable). But a project coming up later this year will be a refactor of trimet.org. For that project, although there will be some mapping aspect, I think it's going to be a much different feel than the current MOD beta map. Whoever ends up developing that app, there will be an expectation of reuse of many of the OTP components developed here...