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
{{ message }}
Repository navigation
Extract graph schema validation into properly named test #3735
Hi @T4rk1n 👋
I'd like to work on this issue! I understand the fix involves extracting check_graph_config_shape(dash_dcc) into its own dedicated test. Is this still available to work on?
Starting on it now!
While investigating, I noticed that the referenced code (check_graph_config_shape) appears to have been removed in PR #3737 ("Add displayNotifier to Graph config props"). I can't find the helper or its invocation in the current dev branch.
Is there a current location where this validation still exists, or has the issue effectively been resolved by subsequent changes?
While investigating, I noticed that the referenced code (check_graph_config_shape) appears to have been removed in PR #3737 ("Add displayNotifier to Graph config props"). I can't find the helper or its invocation in the current dev branch.
Is there a current location where this validation still exists, or has the issue effectively been resolved by subsequent changes?
The test was removed since it was in another tests, the idea was to take the assertion removed in #3737 and make it's own tests and fix the new config.
Activity
siva1104 commentedon Jun 6, 2026
Hi @T4rk1n 👋
I'd like to work on this issue! I understand the fix involves extracting check_graph_config_shape(dash_dcc) into its own dedicated test. Is this still available to work on?
Starting on it now!
siva1104 commentedon Jun 6, 2026
Hi! I'm looking into this issue.
While investigating, I noticed that the referenced code (
check_graph_config_shape) appears to have been removed in PR #3737 ("Add displayNotifier to Graph config props"). I can't find the helper or its invocation in the currentdevbranch.Is there a current location where this validation still exists, or has the issue effectively been resolved by subsequent changes?
T4rk1n commentedon Jul 8, 2026
The test was removed since it was in another tests, the idea was to take the assertion removed in #3737 and make it's own tests and fix the new config.