Increase tn_priority
max value to 9999999999
#166
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
I want to use the current timestamp (epoch) to sort the tree nodes by creation date, e.g.,
1726814949
. Althoughpriority_max = 9999999999
in__get_node_order_str
:django-treenode/treenode/models.py
Lines 461 to 468 in 5663c5b
the maximum value of the
tn_priority
field is set toMaxValueValidator(9999)
:django-treenode/treenode/models.py
Lines 113 to 117 in 5663c5b
My current workaround is to overwrite the
tn_priority
field in my own model:This pull request increases the maximum value for
tn_priority
to9999999999
, enabling the use of timestamps for sorting and aligning it with thepriority_max
value in__get_node_order_str
.Checklist before requesting a review