Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve JSON testing for NamedOperationResolver #3207

Open
GCHQDeveloper314 opened this issue May 7, 2024 · 0 comments
Open

Improve JSON testing for NamedOperationResolver #3207

GCHQDeveloper314 opened this issue May 7, 2024 · 0 comments
Labels
enhancement Improvement to existing functionality/feature named-operation Specific to/touches Named Operations

Comments

@GCHQDeveloper314
Copy link
Member

Describe the improvement you'd like
Testing for NamedOperationResolver should cover configuration of a named operation depth using JSON.

Why do you want this improvement?
Although not yet documented, if admins want to adjust the depth this is currently the only way to do it. As such it should be fully tested.

Additional context
See #3174 where the depth limit was added and #3176 which might indicate part of how to add this testing.

@GCHQDeveloper314 GCHQDeveloper314 added enhancement Improvement to existing functionality/feature named-operation Specific to/touches Named Operations labels May 7, 2024
@GCHQDeveloper314 GCHQDeveloper314 added this to the Medium Term Backlog milestone May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement to existing functionality/feature named-operation Specific to/touches Named Operations
Projects
None yet
Development

No branches or pull requests

1 participant