[Yaml] Support tagged scalars #22762
Merged
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
|
missing CHANGELOG updates in components (please check any your other PRs also if any) |
|
@nicolas-grekas note added |
aeb8050 to
1dea536
Compare
|
done |
xabbuh
reviewed
May 25, 2017
| @@ -21,6 +21,12 @@ CHANGELOG | |||
| the parser and dumper is no longer supported, pass bitmask flags instead | |||
| * the constructor arguments of the `Parser` class have been removed | |||
| * the `Inline` class is internal and no longer part of the BC promise | |||
| * added support of tagged scalars. | |||
fabpot
added a commit
that referenced
this pull request
Jun 14, 2017
This PR was merged into the 3.4 branch. Discussion ---------- [Yaml] Deprecate using the non-specific tag | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | no | New feature? | no <!-- don't forget updating src/**/CHANGELOG.md files --> | BC breaks? | no | Deprecations? | yes | Tests pass? | yes | Fixed tickets | | License | MIT | Doc PR | Values tagged with the non-specific tag must not be transformed in an integer, this tag means that they must not be evaluated (see [the spec](http://www.yaml.org/spec/1.2/spec.html#tag/non-specific/)). I applied this change in #22762 to comply with the spec. Commits ------- 60f5046 [Yaml] Deprecate using the non-specific tag
symfony-splitter
pushed a commit
to symfony/yaml
that referenced
this pull request
Jun 14, 2017
This PR was merged into the 3.4 branch. Discussion ---------- [Yaml] Deprecate using the non-specific tag | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | no | New feature? | no <!-- don't forget updating src/**/CHANGELOG.md files --> | BC breaks? | no | Deprecations? | yes | Tests pass? | yes | Fixed tickets | | License | MIT | Doc PR | Values tagged with the non-specific tag must not be transformed in an integer, this tag means that they must not be evaluated (see [the spec](http://www.yaml.org/spec/1.2/spec.html#tag/non-specific/)). I applied this change in symfony/symfony#22762 to comply with the spec. Commits ------- 60f5046661 [Yaml] Deprecate using the non-specific tag
fabpot
approved these changes
Jul 6, 2017
|
Thank you @GuilhemN. |
fabpot
added a commit
that referenced
this pull request
Jul 6, 2017
This PR was merged into the 4.0-dev branch. Discussion ---------- [Yaml] Support tagged scalars | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes, replacement of deprecations | BC breaks? | yes | Deprecations? | no <!-- don't forget updating UPGRADE-*.md files --> | Tests pass? | yes | Fixed tickets | | License | MIT | Doc PR | Add support of tagged scalars in 4.0. Commits ------- b1e8ebc [Yaml] Support tagged scalars
Merged
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.
Add support of tagged scalars in 4.0.