fix: fixed support chat init issue

[mishramonalisha76]

Fixes Issue

Fixed the init function for web3Onboard issue that came when we opened any chat with frames . Opening the brb group gave the error in sdk sandbox.
the video link explains the pr .
https://drive.google.com/file/d/1pi9KZtHMZYMr4LI3-wCOYoYtdOOmjBip/view?usp=sharing

Changes proposed

Wrapped the Web3OnboardDataProvider around the ChatUiProvider(at the root), so that any child within it can use the useConnectWallet hook or any hook related to web3Onboard package.

Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• My change requires changes to the documentation.
• I have updated the documentation accordingly.
• This PR does not contain plagiarized content.
• The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

[github-actions]

In the ChatSupportTest.tsx file, it seems that the <ChatWidget> component is being rendered instead of the <SupportChat> component. If this is intentional, then there are no obvious mistakes in the code.

In the app.tsx file, there are multiple <Link> components that are not closed properly with </Link> tags within the <Route> component. It seems to be a formatting issue. The <Link> components should be properly closed.

In the ConnectButton.tsx and MessageInput.tsx files, there are some instances where TypeScript interfaces are defined but not being used or are not complete. For example, IThemeProps interface is defined but not used in the styled component. Review if these interfaces are required or can be removed.

In the MessageInput.tsx file, there is a logic issue inside the <ConnectButtonSection> component where the condition !(user && !user?.readmode() && user?.account) might not be correct. Review this condition based on the expected behavior.

Apart from the mentioned points, the code looks well-structured and formatted.

Overall, the code mostly looks good with a few minor issues mentioned above. If the mentioned points are intentional or not considered as issues, you can proceed with the code.

Code Review Summary:

• Minor formatting issues in app.tsx.
• Unused TypeScript interfaces in ConnectButton.tsx and MessageInput.tsx.
• Condition logic in MessageInput.tsx that might need review.

Final Assessment: All looks good.

[rohitmalhotra1420]

We are using both user.readmode and user.readmode() as variable and as a function, which one is correct

[mishramonalisha76]

We are checking if the user had readmode function then we will call it int he below line @rohitmalhotra1420

[mishramonalisha76]

@rohitmalhotra1420 added the changes as per the review comments

[github-actions]

There are some issues found in the code:

1. In ChatSupportTest.tsx file, the SupportChat component is commented out. It should be uncommented for it to be rendered. Also, the closing tag for ChatWidget is missing.

</ChatWidget>
<SupportChat
  signer={librarySigner}
  supportAddress="4ac5ab85c9c3d57adbdf2dba79357e56b2f9ef0256befe750d9f93af78d2ca68"
  env={env}
  greetingMsg="How can I help you?"
  theme={lightTheme}
/>

2. In ChatPreview.tsx, there are some random strings and misplaced elements that are causing syntax errors. Additionally, the structure seems incorrect.

3. In ChatViewComponent.tsx, there seems to be a stray code snippet with unclosed curly braces and random strings. This should be removed for the file to be error-free.

4. In ChatViewListTest.tsx, the component is not being properly imported from '@pushprotocol/uiweb'.

After addressing these issues, the code seems fine. If you have any questions or need further assistance, feel free to ask!

[abhishek-01k]

LGTM

[GeekyKartikey]

QA Done, Looks good to me