This week has been a challenging week. My task has been very challenging
because my test results kept giving very funny results. This week I have
been working on the issue
https://github.com/openwisp/django-netjsonconfig/issues/55
So far i was tried various options with ajv to make sure the json is
validated correctly. I also tested the schema against the sample data on
http://jsonschemalint.com in order to make sure the validator within the
advancedmode editor was not working correctly and it turned out it was not
actually working correctly.
I then took about the whole of Wednesday and thursday to test out the
editor with same configs but out of the django-netjsonconfig app itself.
This version of the editor worked and validated the data properly without
any errors. This therefore made me understand that the problem was actually
with the editor within the app not the validator within the editor.
          So currently, following the recommendations of my mentor,
nemesisdesign, I am working on making disabling schema validation on any
call of the advanced mode editor possible.
           The findings of this week have made me understand that the
current  nature of integrations of the editors into the platform may affect
the performance of the editor in some cases. And I expect this validation
issue to be fixed by the time I am done with my project because the final
library built will be a lot cleaner and have less conflict.
          For next week I am going to be setting up my project working
environment, gathering resources and getting my project plan ready to start
work effectively.
          My experience this week has been basically challenging, because i
had to carry out a lot of tests, just to find out the problem. and not to
even solve it. But I believe it makes me understand the need for my project
to be implemented fully and effectively.

-- 
You received this message because you are subscribed to the Google Groups 
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to