build(deps): bump github.com/mitchellh/mapstructure from 1.1.2 to 1.4.3 in /api

[dependabot]

Bumps github.com/mitchellh/mapstructure from 1.1.2 to 1.4.3.

Changelog

Sourced from github.com/mitchellh/mapstructure's changelog.

1.4.3

• Fix cases where json.Number didn't decode properly GH-261

1.4.2

• Custom name matchers to support any sort of casing, formatting, etc. for field names. GH-250
• Fix possible panic in ComposeDecodeHookFunc GH-251

1.4.1

• Fix regression where *time.Time value would be set to empty and not be sent to decode hooks properly GH-232

1.4.0

• A new decode hook type DecodeHookFuncValue has been added that has access to the full values. GH-183
• Squash is now supported with embedded fields that are struct pointers GH-205
• Empty strings will convert to 0 for all numeric types when weakly decoding GH-206

1.3.3

• Decoding maps from maps creates a settable value for decode hooks GH-203

1.3.2

• Decode into interface type with a struct value is supported GH-187

1.3.1

• Squash should only squash embedded structs. GH-194

1.3.0

• Added ",omitempty" support. This will ignore zero values in the source structure when encoding. GH-145

1.2.3

• Fix duplicate entries in Keys list with pointer values. GH-185

1.2.2

• Do not add unsettable (unexported) values to the unused metadata key or "remain" value. GH-150

1.2.1

... (truncated)

Commits

• b9b99d7 update CHANGELOG
• 13b6df7 Merge pull request #257 from bogdandrutu/smalltypo
• f41e93f Merge pull request #261 from onlyice/feature/json-number-to-uint64
• ea0720b Fix unittest
• 8b0346e Add support for parsing json.Number to uint64
• 6faef11 Fix typo in test name
• 5ac1f6a CHANGELOG
• 18f04e6 Default MatchName in NewDecoder
• 14df28d Merge pull request #247 from veikokaap/fix-doc-typo-decodehook
• 251d52b improve comments for matchname
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated]

This PR has 6 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +3 -3
Percentile : 2.4%

Total files changed: 2

Change summary by file extension:
.mod : +1 -1
.sum : +2 -2

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[dependabot]

Superseded by #217.