Tolerate trailing semicolon in RabbitMQ connection string #875
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.
Usually, database connection strings contain a trailing semicolon after the last "key=value;" pair.
I'm proposing this change to respect the principle of least astonishment and keep RabbitMQ connection strings consistent with other connection strings in the application configuration. I spent some time today figuring out what's wrong; I hope it'll save other people's time in the future, too.
An alternative fix would be to change JasperFx.CoreStringExtensions.ToDelimitedArray to use
StringSplitOptions.RemoveEmptyEntries | StringSplitOptions.TrimEntries
as it doesn't seem that any usage in JasperFx repositories is interested in empty entries after splitting a delimited string. (See https://github.com/search?q=org%3AJasperFx+ToDelimitedArray&type=code)Trimming entries won't be needed, too, on the line 244
array[i] = array[i].Trim();
UPDATE: JasperFx/JasperFx.Core#10