-
Notifications
You must be signed in to change notification settings - Fork 71
[FIX] spreadsheet: parasitic render at every click #6145
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
Conversation
| jest.useFakeTimers(); | ||
| model = new Model(data, { external: { geoJsonService: mockGeoJsonService } }); | ||
| jest.advanceTimersByTime(DEBOUNCE_TIME + 10); // wait for the debounce of session.move | ||
| jest.useRealTimers(); |
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 don't understand how this is not more of a problem. Inside every single test there is parasitic renders happening in the middle of the test because of debounced session.move. Idk how we don't have more indeterministic tests ...
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.
Actually scratch that, this is a problem. I'm 80% sure that's why the composer component tests keep randomly failing on my machine ....
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 don't recall if we found a idea to solve this? I only recall the ideas:
- skipping the first debounce
- having an overall mock of the session in the tests but it lead to the import nightmare...
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.
Fixed in another PR :) (In master, because it needed some tweaks in the file structure)
5f8092d to
c5ffee5
Compare
rrahir
left a comment
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.
🚚 50/50 (I hope) on the comments relevance
| jest.useFakeTimers(); | ||
| model = new Model(data, { external: { geoJsonService: mockGeoJsonService } }); | ||
| jest.advanceTimersByTime(DEBOUNCE_TIME + 10); // wait for the debounce of session.move | ||
| jest.useRealTimers(); |
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 don't recall if we found a idea to solve this? I only recall the ideas:
- skipping the first debounce
- having an overall mock of the session in the tests but it lead to the import nightmare...
Since the topbar refactor, a new render is triggered at every single click event, no matter where we click. This breaks every input with `t-att-value`, their content is reset at each click. Task: 4737827
c5ffee5 to
cbf59c1
Compare
|
@robodoo r+ |
Since the topbar refactor, a new render is triggered at every single click event, no matter where we click. This breaks every input with `t-att-value`, their content is reset at each click. closes #6145 Task: 4737827 Signed-off-by: Rémi Rahir (rar) <[email protected]>

Description
Since the topbar refactor, a new render is triggered at every single click event, no matter where we click. This breaks every input with
t-att-value, their content is reset at each click.Task: 4737827
review checklist