RosterAPI improvements (only BareJID items and no nulls) (#1312)

Activities

wojciech.kapcia@tigase.net opened 3 years ago

Followup to discussion in #issue #1311 (and it's PR). Currently RFC doesn't explicitly forbids FullJIDs in roster, but the general consensus is that it's very, very bad idea and should be avoided altogether. To that end we should switch our RosterAPI to use BareJIDs in 9.0

While we would be changing the API we could also make some additional improvements: use collections instead of arrays and avoid returning nulls in favour of empty collections.

wojciech.kapcia@tigase.net commented 3 years ago

I added @Deprecated annotations to the API. One thing I noticed was that internally our implementation used BareJID thus API exposing FullJIDs made no sense...

wojciech.kapcia@tigase.net batch edited 7 months ago

Name	Previous Value	Current Value
Iterations	empty	tigase-server-9.0.0

wojciech.kapcia@tigase.net added to iteration "Candidate for next minor release" 2 weeks ago

Type	Task
Priority	Normal
Assignee	wojciech.kapcia@tigase.net
Version	tigase-server-9.0.0

Iterations

Candidate for next minor release Open
tigase-server-9.0.0 Open

#1311 Closed

Tigase tries to send presence without "from"

Issue Votes (0)

Watchers (2)

Reference

tigase/_server/server-core#1312