Bump Serilog.Expressions from 1.1.1 to 3.4.1

[dependabot]

Bumps Serilog.Expressions from 1.1.1 to 3.4.1.

Release notes

Sourced from Serilog.Expressions's releases.

v3.4.1

• #77 - enable wildcard indexers over dictionary values (@​nblumhardt)
• #79 - use file-scoped namespaces and target-typed new (@​SimonCropp)
• #82 - sample project retargeting (@​jesseclm)
• #80 - recipe for checking whether any unreferenced properties exist (@​adamchester)

v3.4.0

• #74 - add support for formatting short level names in expressions using ToString(@l, 'u3') etc. (@​nblumhardt)

v3.3.0

• #62 - README update, fix custom name resolver example (@​warrenbuckley)
• #67 - support aliasing of built in property names, to ease migration from Serilog.Filters.Expressions (@​nblumhardt)

v3.2.0

• #45 - Concat(s0, s1, ..sN) (@​nblumhardt)
• #46 - use Directory.Build.props to share common settings (@​SimonCropp)
• #47 - use Nullable package for down-level platform support (@​SimonCropp)
• #48 - code cleanups (@​SimonCropp)
• #49 (@​nblumhardt)
  • default to shallow semantics, add optional deep arg to Rest()
  • improve reporting of function argument count mismatches
  • allow user-defined functions to expose optional arguments

v3.1.0

The last of these churny releases for a while! 😅

• #43 - (@​nblumhardt)
  • Allow all functions to accept a LogEvent parameter
  • Adds virtual NameResolver.TryBindFunctionParameter() to support user-defined function parameter types
  • Combine these to implement a Rest() function, usable in templates only, that matches the behavior of {Properties} in Serilog output templates (i.e. all properties not referenced elsewhere in the template or message)

v3.0.0

• #35 - go dependency-free by interning the needed pieces of Superpower; net5.0 target (@​nblumhardt)
• #38 - support ANSI terminal themes in ExpressionTemplate (@​nblumhardt)
• #19 - use the supplied IFormatProvider (if any) in culture-specific formatting operations (@​nblumhardt)

Breaking changes in this release:

• Optional or nullable IFormatProvider arguments added to the various SerilogExpression factory methods
• Optional or nullable TemplateTheme arguments added to the ExpressionTemplate constructors/factory methods

v2.0.0

• #30 - {#if ...} {#else if ...} {#else} {#end} conditions, {#each ... in ...} {#delimit} {#else} {#end} repetition (@​nblumhardt)
• #31 - make the format argument of ToString(x, format) optional (@​nblumhardt)

Commits

• 25c6509 Merge pull request #78 from serilog/dev
• 56f298e Update README.md
• ae53dab Merge pull request #80 from serilog/adamchester/check-empty-object-readme
• 0fcbae0 Merge pull request #82 from jesseclm/step-sample-project-framework
• 3244505 step sample project target framework
• f3be624 Merge pull request #79 from serilog/cleanup
• 02cdd88 Add a recipie for checking if an object is empty
• 56435a3 file scoped namespace and target typed new
• 94645ab Merge pull request #77 from nblumhardt/additional-wildcard-cases
• 08e7700 Build fixes
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[pull-request-quantifier-deprecated]

This PR has 2 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       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.csproj : +1 -1

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 detected.
• 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.