Draft: introduce strict mode

[hbusul]

This is for issue #87
I've added a first draft of the strict mode, to sum up the changes:

In parser.py I've added UnregisteredPartException which is a subclass of the ParseFailedException.
It has an additional field part_name so you can get what was the name of the unregistered field.

StreamingFormDataParser init function has an extra keyword argument strict which defaults to False.
And it passes this argument to ctor of _Parser.

In pyx file. I've added a new number in ErrorGroup. _Parser has 2 new fields, strict and unknown_part.
The latter one is public, ctor sets the strict mode. And when we are switching the active target, if the new
target is an unregistered one, we set unknown_part , mark_error and return new code from the enum.

@siddhantgoel I would appreciate if you could take a look at it :)

[siddhantgoel]

Overall looks like it'll work! Just left some minor naming suggestions and looks like the CI needs to be made green to be able to merge this in.

[hbusul]

Overall looks like it'll work! Just left some minor naming suggestions and looks like the CI needs to be made green to be able to merge this in.

I'm testing locally with flask to see if I get the exception. I've done the changes you have mentioned. I guess still documentation and tests are missing. I guess I should also write documentation and tests right? It would be nice to mention in the documentation this ParseFailedException as well in addition to UnexpectedPartException

[siddhantgoel]

I guess still documentation and tests are missing. I guess I should also write documentation and tests right? It would be nice to mention in the documentation this ParseFailedException as well in addition to UnexpectedPartException

Yeah, maybe another section in docs/index.rst and at least one parser test to make sure that the exception is raised in strict mode.

[hbusul]

I've added some docs and a test for testing the strict mode

[siddhantgoel]

Awesome, looks good to me! I'll merge it in and try to push a release by the coming weekend.

[hbusul]

@siddhantgoel sorry to bother but did you have a chance to look at the release? Cause I would really like to use this library :D

[siddhantgoel]

No worries, thanks for the reminder as I had completely forgotten about this, so sorry about that!

But v1.13.0 should be available on PyPI now!

[hbusul]

yes it is there, thanks a lot!