In the data sent I saw both active and active_tab.
It was an easy fix for me (I just made sure the parameter in kwargs was named the same as the class variable), but I thought other might get into the same problem, so i'm reporting it as a bug.
You can see the problem in action in this branch in the validation example:
I'm sorry if I overlooked any of this in the documentation, but I'm not sure whether this should work?
There might also be other reasons to send a parameter to kwargs without assigning it to the component?
On a side note I have had a couple of issues previously with the "Checksum does not match" error. I'm not sure what is checksumed, so might add that to the documentation some place?
Anyhow, impressive progress on the project. It has come a long way so far and keeps getting better!
The text was updated successfully, but these errors were encountered:
frbor
changed the title
"Checksum does not match" when kwarg is not defined on class
"Checksum does not match" when kwargs paraemter is not defined on class
Jan 31, 2021
frbor
changed the title
"Checksum does not match" when kwargs paraemter is not defined on class
"Checksum does not match" when kwargs parameter is not defined on class
Jan 31, 2021
Thanks for the bug report (again!). I can replicate this issue, so hopefully I can fix this pretty quickly.
I will try to document the "Checksum does not match" error somewhere as well. I added some code to potentially alleviate it, but it basically happens when a page "gets out of sync" and Unicorn can't figure out what the correct state should be. I'll continue to try to reduce how frequently that happens as I see it in testing.
I just released 0.18.1 which should allow component kwargs to differ from component attributes again. Closing for now, but I added a note to adamghill/django-unicorn.com#2 to document checksums somewhere in the docs.
I upgraded to 0.18.0, but started to see responses with
on one of the pages.
My problem was a component like this:
In the data sent I saw both
active
andactive_tab
.It was an easy fix for me (I just made sure the parameter in kwargs was named the same as the class variable), but I thought other might get into the same problem, so i'm reporting it as a bug.
You can see the problem in action in this branch in the validation example:
I'm sorry if I overlooked any of this in the documentation, but I'm not sure whether this should work?
There might also be other reasons to send a parameter to kwargs without assigning it to the component?
On a side note I have had a couple of issues previously with the "Checksum does not match" error. I'm not sure what is checksumed, so might add that to the documentation some place?
Anyhow, impressive progress on the project. It has come a long way so far and keeps getting better!
The text was updated successfully, but these errors were encountered: