-
Notifications
You must be signed in to change notification settings - Fork 11
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
Fix 124 identifiers sha #135
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
updated cobra and viper package versions
…_sha # Conflicts: # go.mod # go.sum
…o/gleaner into fix_129_context
Tests to be sure arrays are not mangled by string and that strings are not mangled by array.
Tests to be sure arrays are not mangled by string and that strings are not mangled by array.
This reverts commit 613b709.
Tests to be sure arrays are not mangled by string and that strings are not mangled by array.
return an identifier sha if someone asks for an unsupported string add user metadatadetails to s3
…the original later Clean up LdProc Normalize Tests. Empty triples will be empty triples
add some comments to the test
fix workflow
and glcon tools jsonld: jsonld > corrected jsonld rdf: jsonld > rdf
and glcon tools jsonld: jsonld > corrected jsonld rdf: jsonld > rdf
Added ability to just generate a sha of the json. Was option, but not coded.
* Cleaned up tests. Files now used. Added ability to just generate a sha of the json. Was option, but not coded.
…x_124_identifiers_sha # Conflicts: # go.mod # go.sum # internal/common/identifier_test.go # internal/config/sources.go # pkg/cli/gleaner.go # pkg/cli/root.go
…one. What we need is the contexts, for the triples if it falls through to a normalizedsha
…one. We need is the contexts, for the triples if it falls through to a normalizedsha makefile. copy binaries up to that assets are in correct location relative to binaries
But for integration testing file is not run from this directory, so the generation may fail, and gives a warning which muck with an approval test.
This seems to be working for me! Ship it. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add ability to set an identifier per source:
identifiertype
identifierpath is a jsonpath that gets prefied to the default jsonpath.
Metadata about identifier is written to s3 user metadata.
includes the context repairs since that was the most likely normalize issue.