Skip to content
This repository has been archived by the owner on Oct 17, 2023. It is now read-only.

message namespace no longer includes a "db" #258

Merged
merged 1 commit into from
Feb 3, 2017
Merged

Conversation

jipperinbham
Copy link
Contributor

@jipperinbham jipperinbham commented Feb 1, 2017

  • CHANGELOG.md updated

there's never a case where the "db" portion of the namespace was used downstream so this change removes the expectation of needing to "split" the namespace to obtain the table/collection name.

fixes #221

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 59.789% when pulling c044169 on 221-better-ns into 0f7fd11 on master.

@jipperinbham
Copy link
Contributor Author

once #255 is merged I'll rebase and update the etcd adaptor

@jipperinbham
Copy link
Contributor Author

this is ready for review since #255 is deferred until later

@@ -29,12 +29,15 @@ type Msg interface {
Namespace() string
}

// Namespace aliases the string type
type Namespace string
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We convert back and forth all internally... the interface exposes the namespace as a string so I don't think we're gaining anything with this alias.

there was no reason to have Namespace be two parts as every adaptor was just splitting and throwing away the first portion, then having to re-compute later, this cleans up the processing of Namespace a good bit throughout

fixes #221
@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 59.773% when pulling 704ba20 on 221-better-ns into 0f7fd11 on master.

@trinchan
Copy link
Contributor

trinchan commented Feb 3, 2017

LGTM 👍

@jipperinbham jipperinbham merged commit df11d32 into master Feb 3, 2017
@jipperinbham jipperinbham deleted the 221-better-ns branch February 3, 2017 18:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Namespace passing/processing is cumbersome
3 participants