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
value|defaultValue={Symbol|Function} should be ignored, not stringified #11734
Comments
|
Now that I looked at this again, the update codepath was already broken. This just made the initial code path match it. So this is actually an improvement. We should still get #11741 to completion to have consistent sane behavior, but IMO this is not as urgent as I thought at first. |
- the capture attribute changed in #11424 - changes to value/defaultValue handling of functions/Symbols are from #11534, but as per #11734 (comment) this is actually not a new problem so we're okay with it
|
Is it resolved or can I start working on it? Sorry new to open source |
|
I think the issue still exists, it’s just more consistent now |
|
just for reference how do you call dibs on a bug |
|
You got it |
|
Ping @highskillzz, do you still on this issue? If not, I will take it, ok @gaearon |
|
Sure |
|
What's the status on this one? It doesn't seem like this has been resolved since there are no warnings on assigning symbols or functions to the |
|
Feel free to grab it. I don't know if it's fixed or not but it's worth checking. |
|
@gaearon is this still open? if so, how do i claim it? |
|
@krrishdholakia Yes this is still up for grabs if it is not already fixed! Feel free to start looking into it and reach out if you have any issues along the way. |
|
I checked earlier and I might be wrong but I'm quite sure this was fixed earlier by @nhunzaker produces Which indicates that both symbols and functions are not stringified? I've still went ahead and added warnings for the |
|
Although, Both functions get stringified and appended as text into the For reproducing: https://codesandbox.io/s/pj40nrp5px |
|
@raunofreiberg Thanks for looking into that! I agree that textarea should behave the same |
@philipp-spiess Do you mean working on the |
|
@philipp-spiess thanks, are there any other "good first issues" that I could pick up? thanks |
|
@dantesolis You can look for good first issue (taken) and see if there was recent activity. If not, you can usually work on them. In our contribution guides we mention a 2 week period before others can start working on the issue as well. I also think you can take a look at #11299. As far as I know there is still at least one test that uses private API and is not tackled by a community member ( What's also great is if you can improve our test or type coverage. You'd need to research how to find uncovered lines since I don't have a solution for that right now but Jest comes with a coverage tool which might be helpful. Let me know if you're stuck with any of the above steps. |
|
@philipp-spiess then I would be giving issue-12548 a try, since I think someone already asked for #11299 before me, but I'll also keep an eye open for that one. Thanks. About adding coverage, yes, jest comes with coverage. I'll check that one as well. ;) |
|
is it solved ? |
|
What ever happened to this? |
|
I can work on that task? What is needed to finish that task? |
|
Can i look at it? And what is guidelines for contributing? I am new to open source. |
|
Can I take this issue up? |
|
I'm going to work on this issue. |
|
@bvaughn hi I am new here but I want to solve it. |
|
function App() { <textarea defaultValue={() => {}} /> <textarea value={() => {}} /> <textarea value={Symbol("test")} /> ); } |
|
@bvaughn Can i take it, will complete in a week? |
|
Sure. |
|
Hi, @bvaughn may I now take this? I have examined the code and I believe I've come up with a potential solution |
|
Sure. |
|
This problem has been resolved?? |
|
@philipp-spiess @bvaughn Hi guys, what's the latest status of this PR? Is it still open? I was trying out for both <textarea> and , the invalid props warning seemed to work fine. |
|
hey @philipp-spiess is this issue still unresolved , I am new to open source and I would like to give it a try |
|
please let me know some good first issues that I can work on as I am new to open source |
|
I believe mdanyalkhan solved it in his PR #22841. |
|
@gaearon can I start working on this. |
|
Hello, I am Nelson, I am new here and I want to work on the first issue but I need someone to guide me. |




Regression in master from #11534.
Found it thanks to the attribute fixture snapshots.
The text was updated successfully, but these errors were encountered: