-
Notifications
You must be signed in to change notification settings - Fork 36
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 feature to encode and retrieve signac elements by URI. #189
base: feature/integrated-queries
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## feature/integrated-queries #189 +/- ##
==============================================================
- Coverage 65.03% 63.79% -1.25%
==============================================================
Files 37 38 +1
Lines 5554 5626 +72
==============================================================
- Hits 3612 3589 -23
- Misses 1942 2037 +95
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## feature/integrated-queries #189 +/- ##
==============================================================
+ Coverage 65.1% 65.28% +0.17%
==============================================================
Files 37 38 +1
Lines 5574 5657 +83
==============================================================
+ Hits 3629 3693 +64
- Misses 1945 1964 +19
Continue to review full report at Codecov.
|
6df43ad
to
99a5847
Compare
@bdice Is this something that we can integrate with dashboard? |
* Keep signac shell command history on a per-project basis. Resolves issue #134. * Update changelog. * Fix Py27 incompatibility. * Readline module not fully implemented for PyPy.
This patch enables the search for jobs with a statepoint- and document- combined filter. To specify whether a key is a statepoint- or a document-key use prefixes 'sp.' and 'doc.' respectively. No prefix is equivalent to the 'sp.' prefix. This patch is backwards compatible with the exception that the index scheme was slightly modified.
To canonicalize all job-find filters at the JobsCursor stage.
Probably, but I'm not sure if it even makes sense if the URIs require absolute paths. Is there a "relative path" variant of this planned? Like a |
Yes, |
I think this will be a really great feature, I've added it to the milestone for v1.5 |
from ..core import json | ||
from ..common import six |
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.
We can get rid of the py2/3 boiler plate
We should revisit this PR after |
Brief note: We should probably directly support IRIs as a superset of URIs. |
Correct, this is no longer blocked. However, at this point I think we should plan this as a 2.1 feature so that we can focus our immediate efforts on finishing up the changes required for 2.0. I think this is the next major feature on the docket, though. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I don't know how much more work needs to be done here. I'd leave it up to the judgement of @vyasr . |
Sorry for not getting back to this any sooner. I think this is still more appropriate for 2.1. We have enough to get done to get us to a clean state for 2.0 that we'd be better served getting our ducks in line for that and then coming back to this in 2.1. |
Description
This feature implements the ability to encode certain signac elements as a URI which can then be used to retrieve said element with the
signac.open()
function.Minimal example:
Related to issue #96.
Motivation and Context
This change is motivated by the desire to reliably and unambiguously encode signac elements as unique text-strings. It is much easier to copy & paste such a URI and store it somewhere, instead of awkwardly JSON-encoded filter for example.
Types of Changes
1The change breaks (or has the potential to break) existing functionality.
Checklist:
If necessary: