Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in setting the 'lexorank' #64

Open
colideum opened this issue May 13, 2022 · 0 comments
Open

Bug in setting the 'lexorank' #64

colideum opened this issue May 13, 2022 · 0 comments

Comments

@colideum
Copy link

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'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant