fix(tp): allow setting additionalProperties #316
Conversation
This file contains hidden or 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
|
Contributor
|
@MattiasMTS #297 has similar changes and you should be able to set additionalProperties once the PR is merged and released..We are looking to merge this(alongwith some other PRs) and cut a release today. |
Author
I saw #297 got merged and I tried it, still fails. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, adding e.g.
additionalPropertiesto an property defined in tracking plan isn't reflective in the remote tracking plan.I tested this manually on our tracking plans and using the
project.Loadexposed parser.Let me know if you can reproduce!