-
Notifications
You must be signed in to change notification settings - Fork 85
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
Attributions #2591
Attributions #2591
Conversation
@mbc32 I made some small changes and fixed the test. Please let me know if this still works. Also, if you want to order the feature event (not necessary though), you would use something like this: http://docs.grails.org/3.1.1/ref/Domain%20Classes/listOrderBy.html e.g. Cheers |
Hi Nathan, |
I had put that on the get string. I fixed that. 0, but default is |
Hi Nathan, |
This new REST endpoint is for getting User attributions. It is similar to the getHistory endpoint but simpler also it is not used to build the website so changes to the website should not affect this endpoint.
TODO: The test in FeatureEventServiceSpec.groovy has not been tested due to problem with my setup but the code has been tested via REST calls.
I am considering if we should have attributions by organism both because it makes sense to break the attributions down by organism but also because it would make less load on the server if there is a lot of feature events.