Skip to content
This repository was archived by the owner on Oct 3, 2025. It is now read-only.
This repository was archived by the owner on Oct 3, 2025. It is now read-only.

Bug in setting the 'lexorank' #64

@colideum

Description

@colideum

Hi,
Maybe it's a functionality, but anyways. Steps to reproduce:

  • try to add 6 goals or activities or features or mvps one after each other
  • 6th item will not be added because of database constraint, which is related to the rank

When i reviewed the code i've noticed that lexorank is adding ranks interestingly, it always sets mid item between minChar and maxChar, so the first rank in the branch will always be 'm', then it will follow 's', 'v', 'x' and 'y'. After that mid character will still be 'y' as it check with the highest item and then decreases one byte down.

I didn't dig deep into the whole logic, but i think it should be reconsidered or fixed.
But there is still a possibility to avoid the problem by moving 5th item before 4th item. Then 5th will become 'w' and for 6th it still will be possible to add 'y'.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions