blue/squawk
blue/squawk
2
3
Fork 8
Code Issues 23 Pull requests 3 Releases 10 Wiki Activity Actions

Make references in roster #3

New issue
Closed
opened 2019-04-09 11:08:32 +00:00 by blue · 1 comment
blue commented 2019-04-09 11:08:32 +00:00
Owner
Copy link

Technically there is a possibility to have some of your contacts more then one time in roster, for example some contacts may present in a set of groups.
Now I just have multiple instances of a contact and just update n of them if contact change the name for example.
This behavior is unacceptable - I need to make something like references of links nodes to have one contact just liked as many times as user going to need

Technically there is a possibility to have some of your contacts more then one time in roster, for example some contacts may present in a set of groups. Now I just have multiple instances of a contact and just update n of them if contact change the name for example. This behavior is unacceptable - I need to make something like references of links nodes to have one contact just liked as many times as user going to need
blue added this to the 0.1.0 milestone 2019-04-09 11:08:32 +00:00
blue added the
Refactoring
 label 2019-04-09 11:08:32 +00:00
blue modified the milestone from 0.1.0 to 0.2.0 2019-09-15 21:26:01 +00:00
blue commented 2020-04-19 13:16:35 +00:00
Author
Owner
Copy link

Refactored this way. Not sure If I actually like it, the code became more fragile

Refactored this way. Not sure If I actually like it, the code became more fragile
blue closed this issue 2020-04-19 13:16:39 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
encryption
fontMeasure
settings
0.2.3
0.2.2
0.2.1
0.2.0
newMessageFeedPreview1
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.0.5
Labels
Clear labels   
Bug

Something is not working

  
Documentation

Documentation related issues

  
Easy

   
Feature

New feature

  
Localization

Localization related issues

  
Packaging

Issues related to packaging and building

  
Refactoring

Need to reimplement something in a better way

  
Test

Need to test something

No labels
Bug
Documentation
Easy
Feature
Localization
Packaging
Refactoring
Test
Milestone
Clear milestone
No items
No milestone
0.2.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: blue/squawk#3
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?