Fix small bug in ns-registry auto creation #75
Merged
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.
We talked this morning about config variables that specify "Location" and how they should specify the actual filename. I had previously tried to implement some logic that if a file location was passed such as
/foo/bar/
, the namespace registry would auto create the registry database as/foo/bar/ns-registry.sqlite
. Instead of fixing the bug in that logic, let's just say whatever is passed should be considered the file name. A side effect of this is that if the user configuresNSRegistryLocation = /foo/bar/
, the file will be created as/foo/bar/.sqlite
because the code automatically adds a file extension when none is provided and in this case, the actual filename is empty.This fixes #67