Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roster is lower cased #610

Closed
RobertLarsen opened this issue Jun 22, 2015 · 2 comments
Closed

Roster is lower cased #610

RobertLarsen opened this issue Jun 22, 2015 · 2 comments

Comments

@RobertLarsen
Copy link

Rosters provided through ejabberd have the node part lower cased even thou I know that the query that generated it provided mixed casing.

Since we show the received list to the user it would be nice if the original casing would be preserved. Otherwise we will have to make another lookup for each received item which will be wasteful.

This could be configurable so that the default behaviour is the current one.

@zinid
Copy link
Contributor

zinid commented Jun 23, 2015

In order to do this we need to add additional fields in all databases and perform data conversion on the first run to update it. That's pretty much of work. I don't know if any of the developers are motivated that much because I treat this feature as not very important.

@badlop badlop closed this as completed May 24, 2017
@lock
Copy link

lock bot commented Jun 10, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants