feat: lightning/analyticsWaveApi typings updates #530
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
in analyticsWaveApi
|
✅ Reviewed with local linking in VS Code that typeahead for LWCs and Aura components are still working as expected. |
smithgp
approved these changes
Nov 28, 2022
jeffb-sfdc
approved these changes
Nov 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Add typings for
lightning/analyticsWaveApiadapters that have been added since the 238 release. These are all already public and doc'ed. Most of the content here is taken from the types generated by the adapter build and the public docs.What issues does this PR fix or reference?
@W-10758280@, #528