You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a discussion thread to follow on our discussion in the meeting. We agreed that we eventually would like to have a gui for pyElli. A first step could be to implement a REST API for pyElli to interact with any frontend. I think the best technology for us would be fastAPI.
The question here is should we integrate this directly into pyElli or should we add this as a separate package, e.g., pyRElli 😎?
The text was updated successfully, but these errors were encountered:
I quite like the idea of the external API, which allows us to keep the package as simple as possible and not develop the whole API in the main repo.
there may be a case to merge both in the future, if the API can be considered stable. This would prevent the need to update two separate packages for every new version of pyelli.
+1 for fastAPI. I like the simplicity compared to the bigger frameworks.
This is more of a discussion thread to follow on our discussion in the meeting. We agreed that we eventually would like to have a gui for pyElli. A first step could be to implement a REST API for pyElli to interact with any frontend. I think the best technology for us would be fastAPI.
The question here is should we integrate this directly into pyElli or should we add this as a separate package, e.g., pyRElli 😎?
The text was updated successfully, but these errors were encountered: