Skip to content

Feature Request: Add missing types for nested Objects (such as Ads/insights/filtering) #38

@bsless

Description

@bsless

Checklist

  • I've updated to the latest released version
  • I've searched for existing feature requests on GitHub issues
  • I've read the Code of Conduct
  • I've given my issue the title: Feature Request: [name of my feature request]

Goals

Be able to fully validate and describe the API, align to official references documentation

Expected Results

I expect a field like filtering to contain list<FilterObject> or list<AdRuleFilter> and not list<Object>

Code Samples & Details

FilterObject:

{
    "apis": [],
    "fields": [
        {
            "name": "field",
            "type": "string"
        },
        {
            "name": "operator",
            "type": "Filters_operator"
        },
        {
            "name": "value",
            "type": "Object"
        }
    ]
}

Ads/insights/filtering:

                {
                    "name": "filtering",
                    "required": false,
                    "type": "list<FilterObject>"
                },

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions