from_dict ignores extraneous data

Probably related to type validation, but I noticed that dacite ignores extraneous data passed to from_dict.

I expected the last example to also raise an exception.

> @dataclass
> class A:  
>    x: str

> A(x="hello")
A(x='hello')
> A(x="hello", y="world")
TypeError: __init__() got an unexpected keyword argument 'y'

> dacite.from_dict(data_class=A, data={"x":"hello", "y": "world"})
A(x='hello')

[konradhalas]

Let’s choose this option:

from_dict(data_class=B, data=data, config=Config(strict=True))

I will try to implement it in upcoming week.

[jasisz]

I am not sure if this should be a default behaviour though. Such a strict mode IMHO should be enabled by setting it in dacite.Config and with ability to specify where should it be strict.

By “where” I mean the scenario like:

@dataclass
class A:
    x: str
    y: int


@dataclass
class B:
    a: A

data = {
    'a': {
        'x': 'test',
        'y': 1,
    },
    'not_important': 'value'
}

# should not fail, because `a` is ok
from_dict(data_class=B, data=data, config=Config(strict=['a']))

# should fail - strict "from the root level"
from_dict(data_class=B, data=data, config=Config(strict=True))

# should not fail - dafault as now
from_dict(data_class=B, data=data)