-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement django-REST interface #51
Labels
Comments
was extremely simple :-) |
Hacont
added a commit
that referenced
this issue
May 3, 2018
Hacont
added a commit
that referenced
this issue
May 17, 2018
Hacont
added a commit
that referenced
this issue
May 17, 2018
Hacont
added a commit
that referenced
this issue
May 18, 2018
scaphilo
added a commit
that referenced
this issue
May 20, 2018
Hacont
added a commit
that referenced
this issue
Jun 25, 2018
…ration of Accounting and CRM in this area is properly done.
Hacont
added a commit
that referenced
this issue
Jun 27, 2018
Hacont
added a commit
that referenced
this issue
Jun 27, 2018
Hacont
added a commit
that referenced
this issue
Jun 28, 2018
Hacont
added a commit
that referenced
this issue
Jun 30, 2018
Hacont
added a commit
that referenced
this issue
Aug 4, 2018
Hacont
added a commit
that referenced
this issue
Sep 21, 2018
…P header instead. - Google user id in koalixcrm-user header parameter
Basic REST interface is implemented. View specific REST calls are handled in other stories. |
Hacont
added a commit
that referenced
this issue
Oct 14, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To have a standardized interface between potential future customized frontend we should evaluate whether the django-REST interface can fulfill all our needs.
Also the django-REST library will allow us to generate XML and json objects including the refering objects. this will simplify the fixing of issue #18
The text was updated successfully, but these errors were encountered: