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

Fixes the circular JSON TypeError #197

Closed

Conversation

ThinkTankShark
Copy link

No description provided.

@ThinkTankShark ThinkTankShark changed the title Bugfix/circular json Fixes the circular JSON TypeError Sep 25, 2017
@krisk
Copy link
Owner

krisk commented Sep 27, 2017

Thanks @ThinkTankShark, but unfortunately, this cannot be merged. We need an alternative solution that doesn't use external dependencies.

@ThinkTankShark
Copy link
Author

Hi @krisk. Thanks for the response. I didn't realize that I left that external dependency in the code.... It was unnecessary and I removed it. Please let me know if you I need to do anything else to help out. Great module, super useful.

@jeffal
Copy link

jeffal commented Nov 27, 2017

Will this fix be added now that the external dependency has been removed?

@valera-rozuvan
Copy link

@ThinkTankShark Merge conflicts ...

@ThinkTankShark
Copy link
Author

Thank you @valera-rozuvan! Fixed. 👍

@ksloan
Copy link

ksloan commented Dec 15, 2017

Can we merge this please? :)

@grajagandev
Copy link

Would you be interested in software that automatically finds TypeErrors caused by corner cases like circular structures? I am building Fuzz Stati0n to do that (free for OSS) - please take a look and consider signing up for our newsletter to keep in touch.

@Neill83
Copy link

Neill83 commented Jan 2, 2018

hi @krisk,

could you merge this PR please?

Regards

@ksloan
Copy link

ksloan commented Jan 26, 2018

@krisk any updates on this?

@ThinkTankShark
Copy link
Author

@krisk Would you please let us know if this is going to get approved / merged anytime soon or should we close it? I would be more than happy to fix the branch conflicts if it's approved. Thanks

@ksloan
Copy link

ksloan commented Feb 7, 2018

@krisk 🙏

@ksloan
Copy link

ksloan commented Mar 15, 2018

just another monthly checkin on this issue

@ksloan
Copy link

ksloan commented Apr 18, 2018

April check-in, how's this going?

@ksloan
Copy link

ksloan commented May 23, 2018

May-be?

@ThinkTankShark
Copy link
Author

@krisk Can you please update everyone on this PR? Appreciate it.

@ksloan
Copy link

ksloan commented Jun 20, 2018

@krisk

@ksloan
Copy link

ksloan commented Aug 10, 2018

I missed July... my bad. Can we please get this merged for August?!

@krisk krisk closed this in 85bfc87 Feb 5, 2019
@krisk
Copy link
Owner

krisk commented Feb 5, 2019

Well, this was embarrassing on my part. My apologies on the unforgivably long delay, @ThinkTankShark!

There were several conflicts, as the library had been updated a while back, so I incorporated your codebase instead (as merging was slightly nightmarish). Credit given 100% to you though, and noted in v3.3.1 release notes

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.

None yet

7 participants