Refactor database structure of secret objects #528
Labels
needs design
Feature is not fully designed and needs more design work before implementation can start
refactoring
Refactor existing code to make it better
We have: lines, areas, sectors, crags that can be secret. Then we have tags that also have the secret property as I couldn't get an efficient filter to work for the gallery.
My idea to solve this would be a new table only holding the secret property which can then be used for all objects that can be secret. Also we could then write a reusable filter for all the places it is needed. Needs definetely some more thoughts.
The text was updated successfully, but these errors were encountered: