fix: reconnect disconnect deriveds after batch processing #17102
      
        
          +80
        
        
          −2
        
        
          
        
      
    
  
  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.
  
    
  
    
WIP. This is a different take on #17095 — rather than change
is_dirty, which is already a slightly confusing chunk of code, what if we reconnect deriveds after batches are processed? I worry that calling a function calledis_dirtypurely for its side-effects will make things harder to follow in future. We're already breaking the rules by having side-effects inis_dirtyat all, and I would love to find a way to clean that up (other than settingMAYBE_DIRTYsignals toCLEAN, which feels okay).On that: I'm pretty sure we're using terminology incorrectly at present. A derived is
UNOWNEDif it is created outside an active reaction, and as such that flag should never be toggled, unlikeDISCONNECTEDwhich describes the current state of a derived. I feel like this corner of the codebase is overdue for an inspection.Before submitting the PR, please make sure you do the following
feat:,fix:,chore:, ordocs:.packages/svelte/src, add a changeset (npx changeset).Tests and linting
pnpm testand lint the project withpnpm lint