fix: Re-instantiation issue on parent update

[realamirhe]

The updated node for a ref in react life cycle seems to have an issue with react-aptor or plyr which need more time for investigation, I used class selector instead to get the latest version of a video element node by plyr package itself.

It is backward compatible but is a hotfix bug which the user must know, Is there a need for doc update or new version announcement?

let index = 0
const Plyr = React.forwardRef<APITypes, PlyrProps>((props, ref) => {
  // ...
  index += 1

  return (
    <video className={`plyr-react plyr ${index}`}   {...rest}  />
  )
})

result of log statement for first render (<App>0</App>)and second render (<App>1</App>) called in instantiate function

console.log(node, document.querySelector('.plyr-react'))

Fixes: #654

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[vizipi]

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code.
This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below )   Feedback always welcome

Reviewers with knowledge related to these changes

Match %	Person	Commit Count	Common Files
100.00 %	Chintan Prajapati	62	2
100.00 %	Takeshi Iwana	18	2
50.00 %	Tony Narlock	3	1

---

Potential missing files from this Pull request

files commonly committed with a subset of this pr, but not committed this time. (click to collapse)

File	Percentile	rate
package.json	75.00 %	9 out of 12 times

---

Committed file ranks

(click to expand)

99.59%[package-lock.json]

93.42%[src/index.tsx]

[chintan9]

Let me release as alpha version so we can test it.

It is backward compatible but is a hotfix bug which the user must know, Is there a need for doc update or new version announcement?

[realamirhe]

Let me release as alpha version so we can test it.

These are known issues that can be announced to be tested again #654 #605 #511 #654 #474 #562

[realamirhe]

In the overall ref seems to be a better option for dom referencing even in SSRs 😄
But I guess this version can eliminate lots of bugs and we can talk more about the future of it soon.
@chintan9, Is there a way we can contact more often, e.g. via email or social media?