Handle NIL delimiters #27
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.
Without the fix portion of this patch, the test results in the following failure:
Per the RFC 3501 grammar, nil is okay here:
The patch herein defaults to a '/' delimiter for the inbox, but that's probably not the right thing to do either. I would guess one would want to fall back to what NAMESPACE has to say, except in this case, the server I'm dealing with doesn't support NAMESPACE and generally seems to be less than great.
Here's an aggregated trace for your edification / shock and horror at this implementation :)