Skip to content

No way to return values for out parameters when using the optional parameter dispatcher  #221

@hippiehunter

Description

@hippiehunter

Inside traditional bridge, if you're using the version that supports optional parameters there isnt currently a way to deal with out parameters. MaybeOptional treats null as not passed, the web service doesnt expose any user facing fields that would allow the caller to indicate that the out parameter was passed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcustomerissue is impacting a customer

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions