Skip to content
This repository has been archived by the owner on May 30, 2024. It is now read-only.

updated typescript definitions for LDOptions #95

Conversation

stepanataccolade
Copy link
Contributor

  • added missing private fields related configuration options
  • added missing user keys buffer configuration options

Description taken from https://docs.launchdarkly.com/docs/node-sdk-reference site.

- added missing private fields related configuration options
- added missing user keys buffer configuration options
@ashanbrown
Copy link
Contributor

Thanks for the updates. Is there a way we can check typescript coverage in CI?

@eli-darkly
Copy link
Contributor

@ashanbrown I can't think how an automated coverage check could possibly work in this case. These are object properties that aren't defined in any one place in the code. If we were actually writing TypeScript it would be different.

@eli-darkly eli-darkly merged commit 0786d31 into launchdarkly:master Jun 5, 2018
@stepanataccolade stepanataccolade deleted the add_private_attributes_to_LDOptions_ts branch June 6, 2018 11:43
@eli-darkly eli-darkly mentioned this pull request Jun 15, 2018
eli-darkly added a commit that referenced this pull request Aug 22, 2018
fix dependencies with npm audit; add npm audit to CI build
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants