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

Support nullable return type for getCurrentChannel #282

Merged

Conversation

garyadaptive
Copy link
Contributor

According to the specification (https://fdc3.finos.org/docs/1.1/api/ref/DesktopAgent#getcurrentchannel), getCurrentChannel should allow for a nullable return type, but the current type signature does not support this.

Included changes:

  1. In references to getCurrentChannel, change the return type to Promise<Channel | null>

@finos-cla-bot
Copy link

finos-cla-bot bot commented Nov 13, 2020

Thank you for your contribution and Welcome to our Open Source Community!

To make sure your pull request is accepted successfully, we ask all our open source contributors to sign a Contributor License Agreement.

Having reviewed our contributor list, we require a CLA for the following people : (@garyadaptive).

If you need help obtaining a CLA, please read the Requirements for Contributions section of our CLA wiki or email help@finos.org with your questions.

Thanks once again for your contribution. Let us work with you to make the CLA process quick, easy and efficient so we can move forward with reviewing and accepting your pull request.

cc @finos-admin

@rikoe
Copy link
Contributor

rikoe commented Dec 3, 2020

@cla-bot[bot] check

@finos-cla-bot
Copy link

finos-cla-bot bot commented Dec 3, 2020

The cla-bot has been summoned, and re-checked this pull request!

@rikoe rikoe mentioned this pull request Jan 7, 2021
19 tasks
@rikoe rikoe closed this Jan 26, 2021
@rikoe rikoe reopened this Jan 26, 2021
@rikoe rikoe merged commit 5a0b41e into finos:master Jan 26, 2021
@rikoe rikoe added this to the 1.2 milestone Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants