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
Allow the descendant fetcher to be more flexible by grouping uris by model #1275
Conversation
partitioned_uris[:priority] << rdf_resource.subject | ||
else | ||
partitioned_uris[:other] << rdf_resource.subject | ||
rdf_graph_models.each do |model| |
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.
If we're not using the prioritized_object?
method anymore, should it be deleted?
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.
Good catch, I'll take it out.
Is this new behavior API-compatible with old behavior, people setting "priority models" can still set them in the old way and get the same behavior? I think maybe so, can you confirm @cjcolvar ? |
@cjcolvar could it use any more docs explaining this use of |
@jrochkind yes, I was intending to make it backwards compatible. I didn't touch the tests and they still pass |
Awesome, thanks @cjcolvar, appreciate it! |
@jrochkind This is ready for rereview now. |
@cjcolvar Looks like you already have approval and just need a rebase |
This PR preserves previous functionality for grouping uris by priority/other but also adds the capability to get the uris grouped by model if you call
descendant_and_self_uris_partitioned_by_model
directly.