Currently the schema will throw an error if we declare an argument for a LookupArgumentSet that points to another ArgumentSet.
This allows us to support nested query params:
?annotation[key]="my-key"&annotation[value]="my-value"
For example:
module CoreAPI
module ArgumentSets
class MyLookup < Apia::LookupArgumentSet
argument :annotation, type: KeyValue
[...]
end
end
end
class KeyValue < Apia::ArgumentSet
argument :key, type: :string, required: true
argument :value, type: :string
end
Currently we only support string as a valid type an argument of LookupArgumentSet.
Currently the schema will throw an error if we declare an argument for a
LookupArgumentSetthat points to anotherArgumentSet.This allows us to support nested query params:
For example:
Currently we only support
stringas a valid type an argument of LookupArgumentSet.