Skip to content
This repository was archived by the owner on Nov 17, 2020. It is now read-only.

Conversation

michaelklishin
Copy link
Contributor

@michaelklishin michaelklishin commented Jul 21, 2019

Proposed Changes

Names with leading and trailing white space are almost always
a mistake and cause confusion. In a recent support
case they wasted quite a bit of time.

Currently leading and trailing white space in names is very difficult to spot as both management UI
and CLI tools do not highlight white space in names in any way.

This introduces highlighting of leading and trailing white space in queue and exchange names.
Only leading and trailing white spaces, new line characters, vertical tabs and other matches of \s are highlighted, each with a highlighting character. Tabs are highlighted everywhere in the name,
including in the middle. This assumes that tabs are only used in names by mistake (unlike spaces).

The highlighting character is chosen to be the character (Unicode character code: U+23B5) per discussion with the team: it is quite visible on all kinds of screens and would be more obvious than · (U+00B7) and some other options used by developer-oriented tools.

Here's an excellent thread that discusses various options.

This screenshot provides a rough idea of what it looks like:

Screenshot_2019-07-21 RabbitMQ Management

Types of Changes

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (correction or otherwise)
  • Cosmetics (whitespace, appearance)

Checklist

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

Further Comments

[#167415546]

Queue and exchange names, for now.

Currently leading and trailing whitespace in names
is very difficult to spot as both management UI
and CLI tools do not highlight whitespace in names
in any way.

Names with leading and trailing whitespace are always
a mistake and cause confusion. In a recent support
case they wasted quite a bit of time.
@michaelklishin michaelklishin added this to the 3.7.17 milestone Jul 21, 2019
@michaelklishin michaelklishin changed the title Highlight leading and trailing ws in names Highlight leading and trailing white space in names Jul 21, 2019
@michaelklishin
Copy link
Contributor Author

Self-QA'ing and merging as this was demoed to and discussed with the entire team during this week's retro.

Instead of replacing the entire group of characters
with a single block.

While at it, highlight all tab spaces separately,
even in the middle. Unlike spaces, tabs in the middle
of a name were likely used by mistake.
@michaelklishin michaelklishin merged commit 93dba6c into master Jul 21, 2019
michaelklishin added a commit that referenced this pull request Jul 21, 2019
…whitespace-in-names

Highlight leading and trailing white space in names

(cherry picked from commit 93dba6c)
@michaelklishin michaelklishin deleted the highlight-leading-and-trailing-whitespace-in-names branch July 21, 2019 06:38
@michaelklishin
Copy link
Contributor Author

Backported to v3.7.x.

@acogoluegnes
Copy link
Contributor

Small issue in the exchange details link, fixed in 3c89ba5, backported to v3.7.x.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants