Skip to content

Check for redundant properties and implications #16

@ScriptRaccoon

Description

@ScriptRaccoon

Check which implications in the database can be deduced from existing ones (disregarding dualization). These should then be removed. Add this test to pnpm db:test so that every deployment runs it in particular.

Check which (category, property)-assignments (same with non-properties) can be deduced from others BEFORE the deduction script runs. These should not always be removed, since sometimes it is instructive to write down the reasons in the category detail page. But they should be at least marked as redundant on the category detail page, and maybe also logged by the deduction script (pnpm db:deduce).

These checks enforce what is already written down informally in the contribution guidelines.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions