Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/React wrapper props fix #6940

Closed

Conversation

bennyrags
Copy link

Pull Request

πŸ“– Description

The current React.createElement function takes as an parameter the object newReactProps to pass props to the created React component. But we have noticed that some props are not being passed to our React components. When I tested this, I noticed these attributes were not getting passed to newElementProps object but not the newReactProps.

This fix changes the second parameter passed in React.createElement to an object that includes both objects, spread.
After making this fix, all attributes passed from our web components to their React counterparts.

This is my first attempt at contributing and I realize this change may have performance or other implications. I'm not sure this is the correct fix, but it does solve this issue for us. I'd be happy to test performance or anything else with a bit of guidance from your team.

🎫 Issues

#6826

πŸ‘©β€πŸ’» Reviewer Notes

Please let me know if there's anything more you need from me or if there's something you think I'm missing.

πŸ“‘ Test Plan

I ran Lerna tests (and noted this below in the checkbox for tests)
I'd like to test the performance implicaitons of this, but I'm not sure how to do that

βœ… Checklist

General

  • I have included a change request file using $ yarn change
  • I have added tests for my changes.
  • I have tested my changes.
  • I have updated the project documentation to reflect my changes.
  • I have read the CONTRIBUTING documentation and followed the standards for this project.

@bennyrags
Copy link
Author

bennyrags commented Apr 17, 2024

@microsoft-github-policy-service agree company="Thomson Reuters"

@janechu
Copy link
Collaborator

janechu commented May 22, 2024

Closing this issue as we are no longer supporting this package, this is part of ongoing work to re-align the project. My apologies for not addressing this issue beforehand, see #6963.

@janechu janechu closed this May 22, 2024
@janechu janechu added the closed:not-actionable There is no action to be taken in response to this issue. label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed:not-actionable There is no action to be taken in response to this issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants