Juju run-action should not accept parameters not defined in actions.yaml

I have a charm that defines an action (add-peer) with parameters, defined as expected in actions.yaml

When I accidentally called my action with an undefined parameter, it was still passed to the charm code.

This caused issues, since I assumed juju validated that up before passing it to my action.

So, when I ran my code - I ended up with parameters which was undefined but found their way into my code here:

https://github.com/erik78se/charm-wireguard-sub/blob/86d4405872b516e70d71181ae11939989ed5d906/wireguard-sub/src/charm.py#L247

Should juju to accept un-named parameters when calling actions, or should I make this enforced somewhere in actions.yaml ?