Remove value/default inconsistency
#200
Merged
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
In the spec value and default were used exchangeably. Used `default` throughout the spec-files. Fixes: COVESA#198
UlfBj
approved these changes
Oct 13, 2020
|
Discussion if functionality is needed |
|
No strong of opinion as long is it consistent. My personal opinion however is, that neither "default" or "value" needs to be specified in VSS (just look at the current defaults), as this is a deployment question. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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 spec value and default were used exchangeably.
Used
defaultthroughout the spec-files.Fixes: #198