GUACAMOLE-1239: Refactor away need for isCaseSensitive() function of Identifiable. #1036
+464
−277
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.
This change removes the
isCaseSensitive()
function recently added toIdentifiable
to avoid any case where a faulty implementation within one extension'sAuthenticatedUser
, etc. may cause incorrect behavior within the proper implementation of another. Instead, we rely purely on the global configuration setting.This change also:
GuacamoleException
thatgetCaseSensitivity()
may throw, instead providing a default implementation that handles logging of such errors.canonicalize()
convenience function toCaseSensitivity
to abstract away transformation of identifiers into a case-insensitive form.thus avoiding much boilerplate.