Hot fix: resolved merge conflicts, updated UI breaking and updated props docs(rectified redundant code).

[Uyadav207]

What kind of change does this PR introduce?

• Fix made for conflict at 🚀 Feat: Add to airbnb prop explorer #53 and 🔥( Hot-Fix ): fixes UI breaking by error rendering component of (react-view) in playground area.  #76 .....

Did you add tests for your changes?

• Not required...

Summary

• After the merge of feat: Remote docs #15.... there was some conflict occurred resolved that conflict in this PR.

ERROR RESOLVED IS SHOWN BELOW

Does this PR introduce a breaking change?

• No breaking changes are involved.

Other information

• Also removed UI breaking.

before

After (Fixes #75 )

[netlify]

Deploy preview for rne-playground ready!

Built with commit 84d8e04

https://deploy-preview-87--rne-playground.netlify.app

[Uyadav207]

@pranshuchittora, The checks are failing because....

when tried to update the Props folder... it is not pushing....then after looking at this issue... I found that you have pushed the Props folder in .gitignore, That is why ... the checks are not passing as there is no prop folder found.

• What to do now?
• may I remove it from .gitignore?
• This is also causing compilation error on development in the local host....

DO we really need to push the props folder

• Yes, as if not pushed... on the development side... compiler will throw an error NO Such directory found /Props/props.mdx.

[pranshuchittora]

@Uyadav207 this is not required as #15 introduces remote docs for always up-to-dated docs.

[Uyadav207]

ok Got it... @pranshuchittora ... Also The UI for error render is quite buggy may, I give the PR for that instead.

[Uyadav207]

As that changes were included ... in this PR also but no worries

[pranshuchittora]

Sure, Feel free to open a new PR if this can't be updated.

[Uyadav207]

@pranshuchittora, pls help me how can I resolve this??

[Uyadav207]

@pranshuchittora, please have a look...

• after running npm prepare... i.e injecting props... The error is still there... Might be the Case the directory is not found.
• current import STATEMENT
  

[jugshaurya]

@pranshuchittora, please have a look...

• after running npm prepare... i.e injecting props... The error is still there... Might be the Case the directory is not found.
• current import STATEMENT
  

@Uyadav207 , problem is solvable when you run npm i, npm i is running injectProps.js, which is adding Props folder to the appropritate folder. So wait for the #97 to be merged and then run npm i once more to get folder into the codebase/workspace

[Uyadav207]

@pranshuchittora, please have a look...

• after running npm prepare... i.e injecting props... The error is still there... Might be the Case the directory is not found.
• current import STATEMENT
  

@Uyadav207 , problem is solvable when you run npm i, npm i is running injectProps.js, which is adding Props folder to the appropritate folder. So wait for the #97 to be merged and then run npm i once more to get folder into the codebase/workspace

Resolved.. The folder was injected ... but in wrong sub folder