Web and Spark SDK Changes To Enable Application Adoption [DO NOT MERGE] #10
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
mfiess
pushed a commit
to mfiess/Lightning-SDK
that referenced
this pull request
Sep 11, 2019
…-app-crash Hotfix for crash, when component outlives application.
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:
Why:
These changes are for informational purposes only. They illustrate "first pass" changes an application team needed to make in order to effectively use the SDK to build an app that runs on both web and spark platforms using the Lightning SDK, Lightning++ and Lightning stack
NOTE: This was a first pass and does not represent an exhaustive analysis and design for the overall SDK structure.
NOTE: Not included are additional changes needed to the packaging process. These will be submitted in a separate PR.