search

microsoft / BotFramework-WebChat

A highly-customizable web-based client for Azure Bot Services.
https://www.botframework.com/
MIT License
1.6k stars 1.54k forks source link

ReactWebChat - defaultProps will be removed #4836

Open fabricioloupias opened 1 year ago

fabricioloupias commented 1 year ago

Is it an issue related to Adaptive Cards?

No

Is this an accessibility issue?

No

What version of Web Chat are you using?

Latest production

Which distribution are you using Web Chat from?

Bundle (webchat.js)

Which hosting environment does this issue primarily affect?

Web apps

Which browsers and platforms do the issue happened?

No response

Which area does this issue affect?

Development experience

What is the public URL for the website?

No response

Please describe the bug

I am using the react component in version 4.15.9. I find that I get a lot of alerts like "Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead" Clearly in future versions of react, defaultProps is going to be removed.

Do you see any errors in console log?

Warning: EventSpy: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.

Warning: ConnectivityStatusConnecting: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.

How to reproduce the issue?

render

What do you expect?

Release a fix to stop using defaultProps

What actually happened?

-

Do you have any screenshots or recordings to repro the issue?

image

Adaptive Card JSON

No response

Additional context

No response

compulim commented 1 year ago

Thanks for letting us know defaultProps will be removed. We will move our defaults into JavaScript default parameters. :)

compulim commented 1 year ago

Note to myself: when working on this, also fix another React warning which only appears when using Web Chat via npm install.

fabricioloupias commented 6 months ago

any update of this?

donald-boosted commented 6 months ago

any update?

niteshpk commented 6 months ago

any updates? in which version we can expect the fix? Till then do we have any alternative workaround to solve this error?

ayoussef-insight commented 4 months ago

It's been 11 months and this has not been resolved yet. Do we expect a fix soon?

steveberdy commented 2 months ago

I attempted a draft fix of this in #5278. Let me know what you all think