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.

Sign up for GitHub

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

Jump to bottom

Various serialization numbers (REGULAR_TORRENT, CHANNEL_TORRENT, ...) directly used by the GUI #5522

Closed
devos50 opened this issue Jul 23, 2020 · 0 comments · Fixed by #7726
Closed

Various serialization numbers (REGULAR_TORRENT, CHANNEL_TORRENT, ...) directly used by the GUI #5522

devos50 opened this issue Jul 23, 2020 · 0 comments · Fixed by #7726
Labels
type: enhancement

Comments

@devos50
Copy link
Contributor

devos50 commented Jul 23, 2020

In the GUI, we are directly importing stuff from the Tribler core (in table contentdelegate.py):

from tribler_core.modules.metadata_store.serialization import CHANNEL_TORRENT, COLLECTION_NODE, REGULAR_TORRENT

These variables should move to the tribler_common module since they are both used by the core and GUI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

GigaChannel removal qstokkink/tribler
2 participants
@devos50 @drew2a