Closed Tset-Noitamotua closed 2 years ago
This is not intended behaviour. We'll take a look if we can reproduce this and fix it.
Couldn't reproduce with this one https://github.com/eficode/RESTinstance/blob/issue_73/atest/validations.robot#L25
I managed to reproduce this and looks like this fixes the issue. We'll create a PR for that to the Eficode fork once we've written proper unit tests and then create a release PR to this repository.
@Tset-Noitamotua As a workaround you can use skip=true
as the last argument in your Array
keyword to prevent it validating the schema.
I'm still working on an actual solution for this.
The commit I linked earlier did indeed fix this particular issue, but broke something else in the library, so had to revert that change. Moving this from 1.2.0 release to a future release.
Workaround: Use skip=true
to avoid evaluating schema when using assertion keywords.
I created https://github.com/eficode/RESTinstance/pull/19 to fix this issue. The problem was self.request["auth"]
which prevented the use of deepcopy
.
PR is merged. The fix will be available in 1.3.0 release, which we aim to do at the beginning of February. Closing this issue for now.
Then called in sequence the first keyword has an impact on the second.
Question: Is this intended?