-
Notifications
You must be signed in to change notification settings - Fork 36
[BUG] Circular Object. #38
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
Comments
FYI... I saw this when I stored an array of objects in my state:
I'm guessing the confusion was because of the repeated keys in the objects...? |
Well... it's back again, in spite of my work to track / eliminate it.
|
Hello @JESii Thank you for reporting the issue. I will check the issue and let you know. Thanks, |
Thanks, @deeppatel234. FYI I forked the code and searched for "CIRCULER" but was unable to find that anywhere. I did find the section of code where you check for circular structures, but your code specifically resolves down to: |
Hello @JESii and @adamchenwei Circular Object issue is now resolved in useReducer debug. commit 4317bc1 the commit will be release next week. there will be a typo error in the prod extension. the actual text is "CIRCULAR". this is fixed in code but not released. you will find these changes in the next release. Thanks, |
Will Close this issue when released in the store. |
Awesome, Deep — thanks so much!
Jon Seidel, CMC®
… On Jul 24, 2022, at 8:29 AM, Deep Patel ***@***.***> wrote:
Will Close this issue when released in the store.
—
Reply to this email directly, view it on GitHub <#38 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAADZVLL7N2SYF76B3VK7TVVVOO7ANCNFSM5GYQQFVA>.
You are receiving this because you were mentioned.
|
issue is resolved and released in chrome and firefox web store |
Describe the bug
I am seeing the CIRCULAR OBJECT , always in my last item of the events list and there is nowhere describe why its happening.
I saw several related issues, and an open PR.
Which supposedly address this issue? What is the issue exactly? Do we know why its kept recurring?
The open PR I see: #17
Other Same Issue Ref:
#32
#36
#28
The text was updated successfully, but these errors were encountered: