[Feature Request] Split the API calling part into a library

[winstonma]

I love your work on telegram. And I would like to create a MagicMirror Module based on your backend.

I worked on one KMB ETA MagicMirror module and uses js-kmb-api as the KMB ETA API calling library. I really appreciate his work and his work is being used on my MagicMirror module as well as his frontend.

Just wonder if you would consider splitting your API calling code into a separate library so the code can be reused in different projects.

Thanks a lot

[kirosc]

Good idea. Sadly, I don't have any timeline for this. Feel free to fork the repo!

[winstonma]

That's okay.

For my new MagicMirror module to work, if I need to work on the API calling part, I could

• Study the API document
• Drag the backend code onto my module, or
• Create a backend module using your code, and then just call your module

I guess the last option should be the beneficial from a developer perspective but I think it is best if you keep updating the backend module (as you are the original developer). I could try the splitting work. I may start working on this during the weekends so it may take some time to finish.

ATM Let's keep this issue open

[winstonma]

Hi @kirosc

Sorry to let you know that I am using MagicMirror's weather module as a base and this module use XMLHttpRequest (insider weatherprovider.js) which fetches data from the frontend. Therefore I would not need the backend fetcher.

Sorry