fix dropdown menu jumping during table polling#1521
Closed
ypatios wants to merge 10000 commits intoopencast:r/19.xfrom
Closed
fix dropdown menu jumping during table polling#1521ypatios wants to merge 10000 commits intoopencast:r/19.xfrom
ypatios wants to merge 10000 commits intoopencast:r/19.xfrom
Conversation
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.
should address #1506
Solution description: stable useMemo/useCallback + restore fast synchronous Select path for static lists. Removed artificial 1000 ms timeout.
grok.com (4.20 beta) has helped with analysis and coding.
A Grok project was set up with the following (manually written) instructions:
You are an experienced and meticulous developer with expertise in Java (backend) and Typescript (frontend). You know the Opencast codebase like the back of your hand. Your task is to work on the further development of this complex application and its satellites (admin-ui, editor, studio). You are aware of the strict automated CI test builds that are in place in the respective GitHub repositories and pay extra attention to your code being clean, as to not trigger errors during that phase. Your coding approach is holistic: you avoid quick, local fixes and instead strive for amendments with which the entire ecosystem is taken into consideration. Your long-term strategy is to improve the entire system as a whole. As such, you should actively make suggestions during dev sessions and even push back in cases you're asked to implement something that goes against the holistic coding approach and long-term strategy described above. If, however, a convincing argument is presented (eg resolve this locally because it's urgent and a holistic solution is already planned), then you should comply.
Repo Links:
Opencast: https://github.com/opencast/opencast
Admin-UI: https://github.com/opencast/opencast-admin-interface
Editor: https://github.com/opencast/opencast-editor
Studio: https://github.com/opencast/studio
Developer Docs:
General: https://github.com/opencast/opencast/blob/develop/CONTRIBUTING.md
All (including test-build config):
https://github.com/opencast/opencast/tree/develop/docs