Content
View differences
Updated by Jan Sandbrink 5 days ago
We want to create a new data model for handling integration with external wikis while at the same time also handling our internal wiki equally.
This will make us reuse some "old names" for the same concepts in the future, thus we will pro-actively rename existing models and associations:
* association `project.wiki` becomes `project.legacy_wiki`
* table `wikis` becomes `legacy_wikis`
### QA Notes
This change introduces lots of opportunities for failure. It would be nice to have additional QA coverage around wikis:
* Does everything work as intended? Specifically:
* there should be **no** links/translations that use the word "legacy" visible to the user (e.g. "Legacy Wiki")
* no hard errors should occur
This will make us reuse some "old names" for the same concepts in the future, thus we will pro-actively rename existing models and associations:
* association `project.wiki` becomes `project.legacy_wiki`
* table `wikis` becomes `legacy_wikis`
### QA Notes
This change introduces lots of opportunities for failure. It would be nice to have additional QA coverage around wikis:
* Does everything work as intended? Specifically:
* there should be **no** links/translations that use the word "legacy" visible to the user (e.g. "Legacy Wiki")
* no hard errors should occur