Add strict_update flag to update using "status" : "replaced"
#252
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
added 2 commits
July 23, 2024 16:51
danischm
requested changes
Aug 7, 2024
gen/templates/model.go
Outdated
| @@ -83,9 +83,12 @@ func (data {{camelCase .Name}}) getClassName() string { | |||
| return "{{.ClassName}}" | |||
| } | |||
|
|
|||
| func (data {{camelCase .Name}}) toBody() nxos.Body { | |||
| func (data {{camelCase .Name}}) toBody(update bool) nxos.Body { | |||
There was a problem hiding this comment.
Can we maybe name this parameter "statusReplace" instead of "update" to better indicate the purpose? And maybe the same for the schema field: "strict_update" -> "status_replace". What do you think?
|
Hi guys, is there a plan to get this fix implemented? I am unfortunately affected by this situation as well. |
danischm
approved these changes
Dec 17, 2024
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.
Fix #204