[config-editor] VPN servers JSON-schema validation fails

[nemesifier]

How to reproduce:

• go to VPN servers
• add new
• fill in the minimum required information, click save and continue
• now try to go into advanced mode, notice the validation failures, even though the entered JSON is considered valid by other json validation libraries

[gastonche]

working on this now

[nemesifier]

Great, keep us up to date 👍

[nemesifier]

@gastonche have you been able to reproduce the issue?

I thought that it happens because the validation library used by the json-schema editor and the advanced mode editor is different. The one used by json-schema editor works correctly.

[gastonche]

Yeah I thought about that too, I plan on finding a way to modify the validation library in the Advanced JSON Editor

…

On 10 May 2017 at 09:29, Federico Capoano ***@***.***> wrote: @gastonche <https://github.com/gastonche> have you been able to reproduce the issue? I thought that it happens because the validation library used by the json-schema editor and the advanced mode editor is different. The one used by json-schema editor works correctly. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALaC4FHRIhZRdzthnYLXX_mvDhpEWQdAks5r4XVjgaJpZM4NRBhn> .

[nemesifier]

@gastonche if we could configure the advanced editor to use the same JSON-schema validation mechanism of the JSON-Schema UI generator it would be perfect

[gastonche]

Yeah I am trying to do research on that currently.

…

On 10 May 2017 at 13:07, Federico Capoano ***@***.***> wrote: @gastonche <https://github.com/gastonche> if we could configure the advanced editor to use the same JSON-schema validation mechanism of the JSON-Schema UI generator it would be perfect — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALaC4KD8Vowch6QYflof5O9Zub4Znjxtks5r4ahlgaJpZM4NRBhn> .

[nemesifier]

@gastonche any update on this?

[gastonche]

I have been working on this for the past two days and have been getting very funny outcomes. I have tried to use a custom instance of ajv with the advanced mode json editor to no avail. The strange thing with my tests is the fact that when I use an instance of the jsonEditor with out of the django-netjsonconfig with the same configs as with the configs as within the django-netjsonconfig, it does validate correctly. SO right now I don't understand what is wrong. But At least now I know the problem is not with the advanced editor itself. I am using the same files for the test instance as with the netjsonconfig so I am positive that it was supposed to produce the same result. I would like some ideas if any on what may be the problem here. however i continue trying other tests to find out what is the difference.

…

On 18 May 2017 at 11:50, Federico Capoano ***@***.***> wrote: @gastonche <https://github.com/gastonche> any update on this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALaC4IqMdaLLb9u8CsgFrM_qjJszLA8bks5r7CJigaJpZM4NRBhn> .

[nemesifier]

@gastonche Add a way to easily disable the schema validation. I will disable this feature in the VPN management form.

[gastonche]

Okay, will get that done immediately

…

On 19 May 2017 at 10:26, Federico Capoano ***@***.***> wrote: @gastonche <https://github.com/gastonche> Add a way to easily disable the schema validation. I will disable this feature in the VPN management form. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALaC4DC3JiKjOJQuAZDrOmo7BWXP9tLoks5r7WBKgaJpZM4NRBhn> .