saleor-apps-redis_apl/.changeset
Adrian Pilarczyk a32fe7caf4
feat: taxes client logs (#944)
* feat: 🚧 add skeleton logs page

* feat:  add ClientLogsMetadataRepository

* feat:  add AvataxClientLogger and router

* feat:  implement avatax client logs in order confirmed

* feat: 🚧 add skeleton ui for logs

* feat:  add avatax client logger

* refactor: ♻️ move breadcrumbs to page lvl

* feat:  logger per config

* feat:  add logs to remaining events

* refactor: ♻️ pass clientLogger from webhook service

* feat:  add taxjar logger

* test:  add tests for logs push

* feat:  add getAll test

* feat:  add missing taxjar page

* refactor: ♻️ move unshiftItemToLimitedArray to log-utils and test

* fix: 🐛 label

* refactor: 💄 styles

* build: 👷 changeset

* fix: 🐛 typo

* refactor: ♻️ address feedback on backend side

* refactor: ♻️ adjust UI to merging of avatax & taxjar logs

* feat:  make client logs table box scrollable

* fix: 🐛 size of container

* fix: 🐛 loading on isRefetching, not isFetching

* fix: 🐛 no lines early error
2023-09-07 10:42:54 +02:00
..
config.json Setup changesets 2023-02-07 19:40:59 +01:00
honest-geese-crash.md feat: taxes client logs (#944) 2023-09-07 10:42:54 +02:00
mighty-tips-hug.md Update sentry and add Sentry CLI to the workspace (#986) 2023-09-06 10:24:45 +02:00
nine-rivers-flow.md Invoices, Klaviyo: Refactor to shared components (#989) 2023-09-06 12:22:54 +00:00
README.md Update README.md (#649) 2023-06-16 09:06:41 +02:00
real-pigs-promise.md Invoices, Klaviyo: Refactor to shared components (#989) 2023-09-06 12:22:54 +00:00
twelve-pianos-relate.md Invoices, Klaviyo: Refactor to shared components (#989) 2023-09-06 12:22:54 +00:00
wicked-llamas-talk.md Invoices, Klaviyo: Refactor to shared components (#989) 2023-09-06 12:22:54 +00:00

Changeset

Writing guidelines

Rules:

1. Avoid repetition when describing bug fixes

Bad:

Fixed a bug where the component fired confetti uncontrollably when typing into the input. Fixed a bug when...

Good:

The input no longer fires confetti on typing.

2. Use more personal tone

Bad:

It is now possible to use the class xyz directly in…

Good:

You can now use the class xyz directly in…

3. Make it about the user, not the code

Bad:

Added the X and Y fields to the schema returned by Z.

Good:

You can now see how many users are connected to a deployment (X), and the users capacity of the deployment (Y).

4. Use a minimal amount of fluff

Bad:

After many long nights at the office, several cans of beer, and consuming the amount of pizza equal to the surface of a helipad, we finally managed to squash a bug thats been haunting you forever. Its origin reaches back to the times when Tim Berners-Lee…

Good:

The application no longer shuts down when attempting to abort a payment.

5. Use a template when lost

If you dont have an idea how to start, you may use some of those openings:

  • “You can now…”
  • “X no longer does Y when Z.”
  • “X no longer does Y. This means you no longer need to Z.”

6. Describe known issues

When the release introduces some issues or limitations, describe them:

You may experience issues when trying to use the new view with an adblocker turned on. The issue will be fixed in the next release. For now, please…

Resources