This repository was archived by the owner on Oct 9, 2025. It is now read-only.
  
  
  
  
fix(realtime): handle null at convertChangeData #539
                
     Merged
            
            
          
  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.
  
    
  
    
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
When a record is changed, and that record is used by a row-level access policy, the record arriving in the subscription can be null. When convertChangeData tries to Object.keys(record), we get error:
What is the new behavior?
If the record is null, return an empty object to the caller of convertChangeData.
Additional context
Updated also the signature of the call to reflect that
recordcan also benull.