You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just tested the new version and it's working very well. However, I have a question regarding the ID encoding system.
I've noticed that the ID encoding system generates quite high numbers. I understand there might be technical reasons behind this decision, but I'd like to know if it's absolutely necessary to keep these values so high.
Would it be possible to configure or edit the encoding system to start the ID sequence from a lower number, such as 1, to have IDs like 1, 2, 3, 4, etc.? This would make management and tracking much easier for my specific use case.
Thank you for your attention, and I look forward to your response.
The text was updated successfully, but these errors were encountered:
Yes and without any documentation around why it's done, how to build around it and why it's necessary at all, it is super frustrating to work with. No explanation around it makes it infuriating to build with.
Hello,
I've just tested the new version and it's working very well. However, I have a question regarding the ID encoding system.
I've noticed that the ID encoding system generates quite high numbers. I understand there might be technical reasons behind this decision, but I'd like to know if it's absolutely necessary to keep these values so high.
Would it be possible to configure or edit the encoding system to start the ID sequence from a lower number, such as 1, to have IDs like 1, 2, 3, 4, etc.? This would make management and tracking much easier for my specific use case.
Thank you for your attention, and I look forward to your response.
The text was updated successfully, but these errors were encountered: