Fix: Minor import issues in socket-starter-kit #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While setting up Socket for my ETHIndia project, I noticed some minor issues with the import statements in the socket-starter-kit, which I have now fixed.
I’ve submitted this pull request to address those changes- @rookmate , please have a look and merge it if you find it helpful.
Additionally, I’ve documented a few minor issues in the docs in a local text file. While I searched for the repository for these docs (https://docs.socket.tech/), I couldn’t find it in your GitHub organization (https://github.com/SocketDotTech). If possible, I’d be happy to contribute further by addressing these issues—feel free to add me as a collaborator if you’d like me to help with this.
Thank you for taking the time to review this!
Cheers :)