Commit 053d643
committed
chore: bump go-flashduty to v0.14.1 and regenerate
v0.14.1 models /template/update's optional fields as nullable, so the generated
`template update` flags now carry the partial-update contract in their help
text: every channel says "Omit to keep the current content; send an empty string
to clear it", and --team-id says omitting keeps the template's current team.
That wording reaches the skill card's generated fence too, so the card and the
binary now say the same thing.
More importantly the SDK change is what makes clearing possible at all. The CLI
binds its flag map into TemplateUpdateRequest before sending, so while those
fields were value types with omitempty, `--dingtalk-app ''` was dropped by the
encoder and never reached the wire. With pointers it does.
45 files change here but only skills/flashduty/reference/template.md is caused
by the bump. The other 42 are pre-existing drift: the committed generated output
did not match what cligen + skilldoc produce from the SDK main already pinned.
Verified by regenerating on an untouched checkout of main, which produces those
same 42 files. This repo has no generate-drift CI job to catch that, unlike
go-flashduty.
make check-cards reports `skilldoc: cards OK`; build, vet and tests are green.1 parent 21ef2da commit 053d643
45 files changed
Lines changed: 1408 additions & 1425 deletions
File tree
- internal/cli
- skills/flashduty/reference
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
| 6 | + | |
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
4 | | - | |
5 | | - | |
| 4 | + | |
| 5 | + | |
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments