-
Notifications
You must be signed in to change notification settings - Fork 44
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
[REM] UUID: remove fast strategy #5030
Conversation
THe fast strategy for uuid generator was introduced to speed up the startup of a model, specifically when generating cells which could be numerous and the calls to crypto could become a hassle. However, we realised later on that a uuid was useless for that specific purpose. More specifically, a uuid is useful to generate unique identifiers that will be shared accross users to avoid collisions in multi-user context (i.e. concurrent updates). In other cases, shortcutting the uuid generator to become a simple incremented integer value is either wrong or shows the uselessness of calling uuidGenerator in the first place. Task: 4216816
Using uuids in core plugins is either: - wrong if the id is supposed to be shared across users since a different one would be generated for each users. - useless if they aren't shared: the id doesn't need to be unique. This commit removes the `uuidGenerator` from core plugins because it shouldn't be used. The use in the Table plugin was useless (the id is never shared, it's not part of any table core command) Task: 4216816
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I pushed an additional commit to remove this.uuidGenerator
from core plugins to discourage the use of uuids.
What do you think?
robodoo r+ |
@rrahir @VincentSchippefilt because this PR has multiple commits, I need to know how to merge it:
|
robodoo rebase-ff |
Merge method set to rebase and fast-forward. |
THe fast strategy for uuid generator was introduced to speed up the startup of a model, specifically when generating cells which could be numerous and the calls to crypto could become a hassle. However, we realised later on that a uuid was useless for that specific purpose. More specifically, a uuid is useful to generate unique identifiers that will be shared accross users to avoid collisions in multi-user context (i.e. concurrent updates). In other cases, shortcutting the uuid generator to become a simple incremented integer value is either wrong or shows the uselessness of calling uuidGenerator in the first place. Task: 4216816 Part-of: #5030 Signed-off-by: Vincent Schippefilt (vsc) <[email protected]>
Using uuids in core plugins is either: - wrong if the id is supposed to be shared across users since a different one would be generated for each users. - useless if they aren't shared: the id doesn't need to be unique. This commit removes the `uuidGenerator` from core plugins because it shouldn't be used. The use in the Table plugin was useless (the id is never shared, it's not part of any table core command) closes #5030 Task: 4216816 Signed-off-by: Vincent Schippefilt (vsc) <[email protected]>
THe fast strategy for uuid generator was introduced to speed up the startup of a model, specifically when generating cells which could be numerous and the calls to crypto could become a hassle. However, we realised later on that a uuid was useless for that specific purpose. More specifically, a uuid is useful to generate unique identifiers that will be shared accross users to avoid collisions in multi-user context (i.e. concurrent updates).
In other cases, shortcutting the uuid generator to become a simple incremented integer value is either wrong or shows the uselessness of calling uuidGenerator in the first place.
Task: 4216816
Description:
description of this task, what is implemented and why it is implemented that way.
Task: TASK_ID
review checklist