FIX: Busy indicator was not active right after row states were requested #1779
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
so it was not clear that the displayed data was not in final state during scrolling
JindrichSusen
changed the title
|
This pull request has been mentioned on ORIGAM Community. There might be relevant details there: |
now it only triggers the busy indicator
tvavrda
reviewed
Aug 31, 2023
| @@ -28,6 +28,7 @@ import { handleError } from "model/actions/handleError"; | |||
| import { flashColor2htmlColor } from "@origam/utils"; | |||
|
|
|||
| const maxRowStatesInOneCall = 100; | |||
| const loadingDelay = 666; | |||
|
The issue was solved in a different way |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.