Bring vNext up-to-date with respect to master#321
Merged
PerthCharern merged 4 commits intovnextmicrosoft/OpenAPI.NET:vnextfrom Sep 26, 2018
Merged
Bring vNext up-to-date with respect to master#321PerthCharern merged 4 commits intovnextmicrosoft/OpenAPI.NET:vnextfrom
PerthCharern merged 4 commits intovnextmicrosoft/OpenAPI.NET:vnextfrom
Conversation
Release 1.1
- Allow composite expression with the following formats:
- Strings with runtime expression embedded in { }
- Plain strings without any runtime expression
- Strings with {$xxxx} where xxxx doesn't constitute a valid runtime expression is NOT allowed. A set of braces with a dolalr sign denotes a runtime expression in a composite expression and should not be used in other random scenarios.
- Adjust unit tests
…ression Allow composite expression
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Based on #313, vNext should never be behind master. I'm bringing all the changes in master to vNext right now.