Skip to content

Remove _fullInput and other dead transforms code#7834

Open
emilykl wants to merge 10 commits into
v4.0from
remove-fullinput
Open

Remove _fullInput and other dead transforms code#7834
emilykl wants to merge 10 commits into
v4.0from
remove-fullinput

Conversation

@emilykl

@emilykl emilykl commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Addresses #7250

  • The trace._fullInput field existed solely for keeping track of the original input trace after applying defaults but before applying transforms
  • Now that the transforms feature has been fully removed (see Drop transforms from the API #7240, Remove transforms from bundles #7254), trace._fullInput is the same as trace
  • This PR changes all references to trace._fullInput to simply trace, and adjusts logic accordingly
  • Also removes trace._indexToPoints which was likewise only used for transforms
  • Removes some other dead transforms code which was unused but still in codebase
  • Finally, updates or removes tests which referenced trace._fullInput or transforms

This PR should have zero user-facing impact.

@emilykl emilykl marked this pull request as ready for review June 10, 2026 18:50
@emilykl emilykl requested a review from camdecoster June 10, 2026 18:54

@camdecoster camdecoster left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Two things:

  • Could you add a draftlog? Since this removes the deprecated code, it would be good to note that.
  • Could you do a sweep for comments that mention transforms or _fullData?

@emilykl

emilykl commented Jun 10, 2026

Copy link
Copy Markdown
Contributor Author
  • Could you add a draftlog? Since this removes the deprecated code, it would be good to note that.

Sure, I can add a draftlog, it could help with debugging later, so not a bad idea. But the removed code was already inaccessible so I don't expect any user-facing changes.

  • Could you do a sweep for comments that mention transforms or _fullData _fullInput?

Good idea! 0 matches for fullInput, but a bunch of matches for transforms. I'll look at each of those more closely and modify or remove.


// disable 1D transforms (for now)
// Ensure _length is defined
traceOut._length = null;

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all these traceOut._length = null statements refer to disabling transforms... I'm pretty sure they can all be removed after #7240, specifically these lines.

// thing at once manually.
var aStr = 'dimensions[' + initialDimIndex + '].constraintrange';
var preGUI = fullLayout._tracePreGUI[gd._fullData[fullIndices[i]]._fullInput.uid];
var preGUI = fullLayout._tracePreGUI[gd._fullData[fullIndices[i]].uid];

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fullIndices and inputIndices in parcoords are redundant at this point.

@alexcjohnson

Copy link
Copy Markdown
Collaborator

LGTM! Just a couple more items I bet we could remove, as noted above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants