angus
27. Oktober 2022 um 12:16
469
Hallo Leute, wie oben im Thema besprochen, habe ich bereits eine Migrationsfunktion von Retort zu Reactions geschrieben, einschließlich einer Admin-Oberfläche.
I’ve written a migration script and created an admin UI to migrate retorts to reactions. It’s on this branch . The UI looks like this
[Screen Shot 2021-03-18 at 4.30.04 PM]
I need some advice to finish it off.
It’s possible that a user could have both liked and “retorted” on a post. In the migration, I’m going to preference retorts over likes in this scenario. However the ReactionManager.toggle! access protections do not allow this.
Would it be possible to add a “force” option for migrations…
Damit es produktionsreif ist, müssen die Maintainer von Reactions eine kleine Änderung vornehmen, um die Abstraktion des Codes im Reactions-Plugin zu verbessern.
Yup, I could do that. It would be a bit of a hack though
Die Unterstützung einer produktionsreifen Migration zwischen zwei Plugins wie diesem erfordert eine erhebliche Qualitätssicherung, da sonst Probleme wie dieses leicht auftreten können.
What is happening here is this
Some people have a very old version of the question answer plugin with my personal github username in the repository URL in their app.yml file.
I transferred the QnA plugin to paviliondev years ago. Github redirects repository URLs when they’re transferred, so the old urls with my personal username in it kept working.
More years later Pavilion transferred the Question Answer Plugin to Discourse. Discourse initially kept the name discourse-question-answer.
…
4 „Gefällt mir“