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

Should compute the first nested property #51

Open
mateonunez opened this issue Sep 25, 2022 · 1 comment
Open

Should compute the first nested property #51

mateonunez opened this issue Sep 25, 2022 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@mateonunez
Copy link
Owner

In some cases API responses are complex:

{
  "data": {
    "results": {
      "id": "1",
      "name": "John Doe",
      "email": "john@doe.com"
    }
  }
}

The method that computes the first usable property should compute the first nested property, avoiding property specification.

image

@mateonunez mateonunez added enhancement New feature or request good first issue Good for newcomers labels Sep 25, 2022
@mateonunez
Copy link
Owner Author

This could be implemented by adding a new property in the ImpactOptions type: maxDepth.

maxDepth property should indicate how many levels of nested objects will be analyzed to resolve the schema.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant