Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

💥 Add strong types for JSON.parse and JSON.stringify #25

Merged
merged 1 commit into from
Apr 2, 2023

Conversation

aaditmshah
Copy link
Contributor

No description provided.

@uhyo
Copy link
Owner

uhyo commented Mar 28, 2023

Thank you, exciting work 🥰
Allow me to take some time understanding this.

@aaditmshah
Copy link
Contributor Author

Here is some documentation that explains the changes I made in detail.

Let me know if you have any additional questions.

@graphemecluster
Copy link
Contributor

I regret to tell that the repo you mentioned is the biggest rival which upsets the author of this repo. There must be something missing that could further improve this repo such that there are more stargazers.

@uhyo
Copy link
Owner

uhyo commented Mar 31, 2023

It's not that serious 😅 (I still think mine better resets type definitions than theirs though!)

I think I can take time for review on this weekend. Thanks for additional explanation!

Copy link
Owner

@uhyo uhyo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it! Thank you 🙌

@uhyo uhyo merged commit 067fba0 into uhyo:master Apr 2, 2023
@aaditmshah aaditmshah deleted the feature/json branch April 2, 2023 11:58
@aaditmshah
Copy link
Contributor Author

I regret to tell that the repo you mentioned is the biggest rival which upsets the author of this repo.

I completely understand.

There must be something missing that could further improve this repo such that there are more stargazers.

I believe adding more comprehensive documentation, creating video tutorials and screencasts, and advertising via word of mouth should increase the popularity of this library significantly.

It's not that serious 😅 (I still think mine better resets type definitions than theirs though!)

Oh, yes. 100%. Using @typescript/xxx packages is the right way to reset the type definitions. It actually replaces the incorrect types instead of simply adding alternative type definitions, which from my personal experience is problematic as you can still use the incorrect type definitions.

I think I can take time for review on this weekend. Thanks for additional explanation!

Thank you for approving and merging my changes so quickly. Let me know if there's any other way I can help make this library better.

Also, pardon my forthrightness but when will the next version of this library with my changes be released?

@uhyo
Copy link
Owner

uhyo commented Apr 2, 2023

I have to upgrade to TypeScript 5.0 before release the next version. I'll take time tomorrow 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants