fullstory-babel-plugin-annotate-react icon indicating copy to clipboard operation
fullstory-babel-plugin-annotate-react copied to clipboard

Fragments still getting (attempted) annotations

Open jarredt opened this issue 3 years ago • 4 comments

I am seeing warnings on both the native and web versions of our app that Fragment elements are being given dataElement props. I have tried without specifying any "annotate-fragments" setting, setting it to false, and setting it to true, but I get the warning no matter what.

Screen Shot 2021-04-14 at 11 48 35 AM Screen Shot 2021-04-14 at 11 48 18 AM

jarredt avatar Apr 14 '21 18:04 jarredt

Hi there @jarredt, RC here with FullStory's support engineering team. We're not set up to troubleshoot issues via Github issues currently. If you're still running into issues here can you reach out to [email protected]? We'll be more than happy to help out.

Thanks so much!

rcmaples avatar Dec 22 '21 14:12 rcmaples

For anyone googling around trying to find a solution to this, add the following

[ '@fullstory/babel-plugin-annotate-react', { native: true, ignoreComponents: ['React.Fragment'] }, ],

shaunp-street avatar Aug 02 '23 09:08 shaunp-street

I am doing exactly what @shaunp-street suggested, but to no avail. Still getting Warning: Invalid prop fsTagNamesupplied toReact.Fragment. React.Fragment can only have keyandchildren props. warnings. Anybody with a solution?

cansin avatar Mar 28 '24 00:03 cansin

@cansin Could you share the source code for how you're using React.Fragment? If you have multiple uses of React.Fragment and not sure which one is causing this error, I suggest narrowing it down to a specific example.

RyanCommits avatar Jul 25 '24 20:07 RyanCommits