Hello ![]()
I’m curious to know what are the technical limitations for this.
An example of my use case would be:
- a topic titled “Local cuisines from Location A are generally saltier compared to local cuisines from Location B”
- where Location A and Location B are category names
- there is a poll with options
Agree,NeutralandDisagree - being able to save the topic under both categories allows syncing of conversations and votes between both categories from day 1 (or hopefully within a few days of topic creation), instead of a reactive approach of only merging duplicate topics after the issue went viral)
- a cool codename for this could be
anti-cross-categories-topic-duplication-feature/pluginlolz
My first thought was to create a middle table in db. Lolz so low level ![]()
Probably some better solutions could be
- add a model class reference or association
- index a list of topics associated with a category in db and call a method to bundle those topics when calling
@category.all_published_topicsor something
So yeah just wanted to know if there’s a strict technical no-no regarding this issue before I dive in deeper ![]()