Add Pan offset props to PropsToFilter

[m-bert]

Description

In Pan gesture, offset properties are handled differently than other props. Before they're sent to native side, they are mapped to separate start and end offset properties. This happens when offset props are present. However, if one explicitly sets value of offset property to undefined, e.g.:

activeOffsetY: Platform.OS === 'android' ? [-75, 75] : undefined,

the following warning can be observed:

WARN  [react-native-gesture-handler] activeOffsetY is not a valid property for PanGestureHandler and will be ignored.

This PR adds offset properties to our filter. With this change, warning no longer appears.

Fixes #4021

Note

It could also be solved by dynamically deleting undefined fields from config, but simply ignoring them sounds safer.

Test plan

Tested on the following code:

import React from 'react';
import { StyleSheet, Text, View, Platform } from 'react-native';
import { usePanGesture } from 'react-native-gesture-handler';

export default function EmptyExample() {
  const panGesture = usePanGesture({
    activeOffsetY: Platform.OS === 'android' ? [-75, 75] : undefined,
  });

  return (
    <View style={styles.container}>
      <Text style={{ fontSize: 64, opacity: 0.25 }}>😞</Text>
      <Text style={{ fontSize: 24, opacity: 0.25 }}>It's so empty here</Text>
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
  },
});

[Copilot]

Pull request overview

Updates the v3 hooks config filtering so Pan offset props that may temporarily exist on the JS config object (especially when explicitly set to undefined) don’t trigger “invalid property” warnings during native config preparation.

Changes:

• Add Pan offset props (activeOffsetX/Y, failOffsetX/Y) to PropsToFilter to suppress warnings when they appear in the config object prior to remapping/deletion.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[m-bert]

or deleting these keys in transformOffsetProp even when the value is undefined

This is what I said in note in the description of the PR. I'm not sure if we want to do this, but it is an option (cc @j-piasecki)

[j-piasecki]

Does passing undefined currently reset the value to the default?

[m-bert]

When you pass undefined it is treated as if it wasn't passed at all.

[m-bert]

Or do you mean alternating between some value and undefined?

[j-piasecki]

Or do you mean alternating between some value and undefined?

Yes