Comment on Introducing nested replies
Richie@meta.discourse.org 4 weeks ago Interesting…
Does this suggest it should be tested in our communities in isolation first, before we all pull the trigger and convert every existing topic? :thinking:
That’d work, providing it supported tens of thousands of topics.
But it’d need to be made very clear that there is no coming back from this :sweat_smile:
Will this feature be implemented here on meta first, or on https://try.discourse.org so we can test it outside of our production environments?
If it were my community I would test in isolation first. On the other hand we would get more valueable feedback faster by you enabling for your whole community :wink: . Jokes aside, I do think testing in isolation is probably smart but there is no destructive data migrations here. It can be enabled and disabled safely. No decision you make here will lock you in either direction.
I guess I sorta accidently answered this part! Enabling nesting simply creates a
nested_topicrecord for each topic in the DB and kicks off a job to calculate reply counts down the ancestry tree. Disabling nesting removes thatnested_topicrecord and you’re back to flat, no issue.Feel free to play with it in this category: