feat!(typescript): align TypeScript definitions with Discovery API #513
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
|
Call Nov 06
|
|
The PR should now be updated as discussed during today's meeting :) Let me know if there is anything that should be changed additionally. |
… API Co-authored-by: danielpeintner <[email protected]>
|
Scripting Call Nov 20
|
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.
In the context of eclipse-thingweb/node-wot#864, I noticed that the TypeScript definitions are not taking into account the latest changes to the Scripting APIs discovery API (see #405 and #441). This PR should adjust the types accordingly – let me know if I missed anything :)