These are chat archives for fossasia/open-event-server

8th
Apr 2017
Shubham Padia
@shubham-padia
Apr 08 2017 13:40
@niranjan94 regarding #3459, what are the advantages of implementing the schema (except maintaining a standard), and since we have to use a different library, i'm assuming the current api has to be ported to whatever library is decided to be implemented ?
Niranjan Rajendran
@niranjan94
Apr 08 2017 13:43

except maintaining a standard

This is the primary goal. Also, we plan to move to a completely API-centric project where even the organizer frontend would use the API for all of its functions. So, when you are going to be depending completely on the API, it important that we maintain certain standards. Also, this would allow us to open up the API for third-party developers to use too in the future. And since it based on a standard spec, it'll be easier for them to use in their apps too

Shubham Padia
@shubham-padia
Apr 08 2017 13:55
:+1:
Although we will have more information from the last time, does this mean writing the existing api from scratch ?
Niranjan Rajendran
@niranjan94
Apr 08 2017 13:57
Not completely ... we can still retain certain aspects of it ... We'll need to write it in a way that we re-use as much as possible ... Time is a constraint here ...
Shubham Padia
@shubham-padia
Apr 08 2017 13:58
How much time do you think this will take, just curious ?
Niranjan Rajendran
@niranjan94
Apr 08 2017 13:59
To be frank ... I'm really not sure at this point ... Haven't gone through all the aspects of this yet ....
The issue has been opened on GH to start discussions on this
Shubham Padia
@shubham-padia
Apr 08 2017 14:00
:+1:
Niranjan Rajendran
@niranjan94
Apr 08 2017 14:01
Feel free to suggest improvements, ideas to make this happen in as less time as possible ... Or even alternative implementations if you have any ...
on the issue
Shubham Padia
@shubham-padia
Apr 08 2017 14:07
:+1: I think after a time constraint is estimated and decided upon, we can discuss more upon whether this move will be worth the time and effort put into it or not, as the current api seems functional enough for the current usage. Not sure if the current API will raise problems when we decouple the frontend or not.
Shubham Padia
@shubham-padia
Apr 08 2017 14:17
Is it an viable option to extend the current api and decouple the front-end or would that also make us end up in a situations where we currently are again ?
Niranjan Rajendran
@niranjan94
Apr 08 2017 14:26
The issue is, the current API, is like patchwork ... If look at it, there are field names that don't make sense to a new person ... some of the newer endpoints seem to look different from older ones ... No standard way to sort, filter fields ...
If you look at the json-api, it's not just a response structure ... It also includes specs for paginations, filtering, sorting, relationships
So, I for one, feel it's worth the work involved on the longer run
The Open Event API is going to be the core of this project ... with all the webapps, android apps, ios apps any other app we make in future using it
So, we need it to be reliable and as close to a standard as possible
Shubham Padia
@shubham-padia
Apr 08 2017 14:29
sounds good :+1:
Niranjan Rajendran
@niranjan94
Apr 08 2017 14:29
Either we define our own well-documented & featured spec (which is hard and like re-inventing the wheel) or we use an existing one ...
Shubham Padia
@shubham-padia
Apr 08 2017 14:30
:+1:
Mario Behling
@mariobehling
Apr 08 2017 14:34
@shubham-padia I think the API approach will bring a lot of advantages. People could even build their own clients in any language they like in future. As we are much clearer than last year about what we need and where we are heading I think with the effort of all contributors we can pull that off within a few months. It would be great if you could take on a leadership position apart from Niranjan.
Shubham Padia
@shubham-padia
Apr 08 2017 14:37
:+1:
Decoupling the frontend and backend will surely bring in a lot of advantages.