chore(deps): update dependency storybook-addon-react-router-v6 to v0.3.6 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
storybook-addon-react-router-v6	0.2.1 -> 0.3.6

---

Release Notes

JesusTheHun/storybook-addon-react-router-v6 (storybook-addon-react-router-v6)

v0.3.6

Compare Source

⚠️ Pushed to main

• fix(router): rebuild router only after story args changed (@​JesusTheHun)
• feat(decorator): add support for shouldRevalidate function (@​JesusTheHun)
• fix(controls): router not reloading component after change through SB controls (@​JesusTheHun)

Authors: 1

• Jesus The Hun (@​JesusTheHun)

---

v0.3.5

Compare Source

⚠️ Pushed to main

• fix: reloading component should not trigger a console warning (@​JesusTheHun)

Authors: 1

• Jesus The Hun (@​JesusTheHun)

---

v0.3.4

Compare Source

⚠️ Pushed to main

• fix: log of action with file upload (@​JesusTheHun)

Authors: 1

• Jesus The Hun (@​JesusTheHun)

---

v0.3.3

Compare Source

⚠️ Pushed to main

• fix: story decorator not passing errorElement to the wrapping component (@​JesusTheHun)
• fix: story decorator not passing routeHandle to the wraping component (@​JesusTheHun)

Authors: 1

• Jesus The Hun (@​JesusTheHun)

---

v0.3.2

Compare Source

⚠️ Pushed to main

• feat: add support for route handle (@​JesusTheHun)

Authors: 1

• Jesus The Hun (@​JesusTheHun)

---

v0.3.1

Compare Source

⚠️ Pushed to main

• fix(ts): restore ts rootDir to src (@​JesusTheHun)
• misc(npm): bump version (@​JesusTheHun)

Authors: 1

• Jesus The Hun (@​JesusTheHun)

---

v0.3.0

Compare Source

Support for data routers

• Route loader
• Route action
• Outlet loader
• Outlet action
• Customizable outlet path
• Loader introspection logs
• Action introspection logs
• Test coverage

Authors: 1

• Jesus The Hun (@​JesusTheHun)

v0.2.2

Compare Source

⚠️ Pushed to main

• feat(readme): add data router information (@​JesusTheHun)
• feat(ci): add tests to CI steps (@​JesusTheHun)
• feat: ts strict (@​JesusTheHun)
• feat: ci (@​JesusTheHun)
• feat: log route loader (@​JesusTheHun)
• feat: log route outlet action (@​JesusTheHun)
• feat: log route action (@​JesusTheHun)
• fix: faulty router initialization (@​JesusTheHun)
• wip: tests (@​JesusTheHun)
• wip: impl (@​JesusTheHun)

Authors: 1

• Jesus The Hun (@​JesusTheHun)

---

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[yanguoyu]

We'd better check whether the storybook runs success before approving it.

[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: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

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.

[yanguoyu]

It will update by nervosnetwork#2747