Skip to content

fix(@ngtools/json-schema): enum values properly handle defaults and null - #4387

Merged
hansl merged 1 commit into
angular:masterfrom
hansl:schema-tree-fixes
Feb 3, 2017
Merged

hansl merged 1 commit into
angular:masterfrom
hansl:schema-tree-fixes

Conversation

@hansl

@hansl hansl commented Feb 3, 2017

Copy link
Copy Markdown
Contributor

NULL are not valid values, and now the default will be respected for enum.

…ull.

NULL are not valid values, and now the default will be respected.
@hansl
hansl force-pushed the schema-tree-fixes branch from 316ae7c to 055d873 Compare February 3, 2017 03:25
@hansl
hansl merged commit ea9f334 into angular:master Feb 3, 2017
MRHarrison pushed a commit to MRHarrison/angular-cli that referenced this pull request Feb 9, 2017
…ull. (angular#4387)

NULL are not valid values, and now the default will be respected.
asnowwolf pushed a commit to asnowwolf/angular-cli that referenced this pull request Apr 12, 2017
…ull. (angular#4387)

NULL are not valid values, and now the default will be respected.
@hansl
hansl deleted the schema-tree-fixes branch August 2, 2018 19:57
@angular-automatic-lock-bot

Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants