animint.js: remove unnecessary Selectors.hasOwnProperty checks#306
animint.js: remove unnecessary Selectors.hasOwnProperty checks#306ANAMASGARD wants to merge 8 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #306 +/- ##
=======================================
Coverage 73.02% 73.03%
=======================================
Files 164 164
Lines 8837 8840 +3
=======================================
+ Hits 6453 6456 +3
Misses 2384 2384
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
tdhock
left a comment
There was a problem hiding this comment.
also please investigate CI failure
|
Sir @tdhock , if(selector_name) guards in Changes 1 and 2 cannot be removed safely — [selector_name] is null on initial geom rendering, so without the guards, Selectors[null].duration throws a TypeError and breaks all 149 JS tests. |
|
ok i see now " [selector_name] is null on initial geom rendering" why and when does that happen? |
Fixes #278. Replaced Selectors.hasOwnProperty(selector_name) with a simple selector_name check in draw_geom and geom_label_aligned. Removed redundant guard in update_selector. Removed Selectors.hasOwnProperty check in update_axes.
…e only
Replace bare if(selector_name) guards in geom_label_aligned and draw_geom
with if(selector_name && Selectors[selector_name].hasOwnProperty("duration"))
to match the same pattern already used in update_axes (Change 3).
…NEWS PR number to PR#306
e766b51 to
008ab95
Compare
Use selector_has_duration() for geom_label_aligned, draw_geom, and update_axes so null selector_name on initial update_geom(g, null) stays safe and we only transition when duration is defined. Remove redundant hasOwnProperty guard in update_selector.
- DESCRIPTION: Gaurav comment -> GSOC 2026 - animint.js: drop git status and Selectors.hasOwnProperty; keep name guard for null selector_name on initial render - NEWS.md: PR#306 attribution and accurate changelog wording
|
Sir @tdhock thanks for the review ,
|
Fixes #278
I confirm I have not used any AI code generation tools for this PR.