akikoskinen

Whoa, that's something I call a thorough answer 🙇 My original problem was that I couldn't tell apart "invalid signature" and "missing required claim" cases (just using the exception type)....

I understand the use cases now. But having an input variable called `register_task_definition` also control the feature `output_json_object_instead_of_array` is very unexpected. Perhaps there should be a dedicated input variable for...

Looks like the documentation is talking about some future dream. The [code explicitly mentions in comments](https://github.com/django-parler/django-parler/blob/5158e08009b80c9573f6f0d440aff4f4aa5c384c/parler/models.py#L1082-L1087) that it isn't supported to change an existing field into a translated field.

Not exactly sure what is wanted here, but I doubt it's possible within the [limits of the current (June 2018) GraphQL specification](http://spec.graphql.org/June2018/#sec--deprecated). The deprecation feature in GraphQL (the specification) is...

Here are files to reproduce this. I took an [existing test file](https://github.com/adorsys/keycloak-config-cli/blob/main/src/test/resources/import-files/identity-providers/20_create_other_identity-provider-with-custom-first-login-flow.json) as a base, slightly modified to suit this case (the filenames have a `.txt` extension, although they are...

Indeed it looks like giving the `--import.managed.client-scope=no-delete` option prevents deletion of pre-existing required actions.

Not directly related to this, but it _could_ work as a solution. I have come to the conclusion that the `@validated` class decorator can't be used in every use case....

> My current idea is to provide a validation function from `graphene-validator`. @chpmrc PR #11 now contains this kind of validation function. Can you check it out?

@chpmrc Would you like to check out this PR and give some comments?