-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature/uppsf 836 change replace endpoint #43
Feature/uppsf 836 change replace endpoint #43
Conversation
newHash := randomdata.RandStringRunes(56) | ||
|
||
const contentID = "83a201c6-60cd-11e7-91a7-502f7ee26895" | ||
fromAnnotationAPI := []annotations.Annotation{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can use expectedAnnotations.Annotations for input and move the response slice outside the test to be consistent with the other tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I explicitly did not reuse any of the already defined structures. I feel that keeping the data next to the code makes for more readable tests and less fragile test suite.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree but if we don't reuse the structures, our code will become very large.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid the code getting too large with such structures we can use fixtures.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a ticket (UPPSF-765) regarding fixing the docs for this service, could you update the README according to that?
newHash := randomdata.RandStringRunes(56) | ||
|
||
const contentID = "83a201c6-60cd-11e7-91a7-502f7ee26895" | ||
fromAnnotationAPI := []annotations.Annotation{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid the code getting too large with such structures we can use fixtures.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems ok, you can squash the last two commits in some of the previous ones, so that we get cleaner history when we merge to master
.
fa39a18
9385377
to
fa39a18
Compare
Enable replace annotation endpoint to accept both concept id and predicate for substitution.
Add
http://www.ft.com/ontology/hasBrand
as a valid predicate identifier.Update healthcheck panic guide urls.
Add documentation for replace endpoint.