Skip to content
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

RESTDao Provider #136

Open
mrobustelli opened this issue Sep 20, 2018 · 5 comments
Open

RESTDao Provider #136

mrobustelli opened this issue Sep 20, 2018 · 5 comments
Assignees
Labels
area/provider Relates to DAO/Provider implementations

Comments

@mrobustelli
Copy link
Contributor

No description provided.

@mrobustelli mrobustelli changed the title Implement RESTDao RESTDao Provider Sep 20, 2018
@Arithmomaniac Arithmomaniac added the area/provider Relates to DAO/Provider implementations label Sep 23, 2018
@mrobustelli mrobustelli added this to Prioritized in Issue Prioritization Sep 24, 2018
@Arithmomaniac
Copy link
Collaborator

We should probably be careful to distinguish between a REST Dao (one that calls REST directly, with no Relativity dependencies) and an ObjectManager Dao.

@KalinaTSD
Copy link
Collaborator

Please provide a proper documentation and I'm going to plan some work here.

@Arithmomaniac
Copy link
Collaborator

Please provide a proper documentation

You mean asides from the REST documentation?

@mrobustelli
Copy link
Contributor Author

@KalinaTSD is picking up this issue. She is going to review the RSAPI implementation and try to mimic for Rest. The goal will be to create several smaller issues, linked to this one and tackle that way. @KalinaTSD will create the issues when she has a good understanding of the RSAPI implementation.

@Arithmomaniac
Copy link
Collaborator

Great.
I would suggest implementing the underlying REST Provider with an ORM like RestEase or Refit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider Relates to DAO/Provider implementations
Projects
Issue Prioritization
  
Prioritized
Development

No branches or pull requests

3 participants