djkato/saleor-apps-redis_apl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
saleor-apps-redis_apl/.changeset
History
Krzysztof Wolski a1ad70e879
Unify urql version, use shared util to create client (#657) 
* Add createGraphQLClient util to shared package

* Update urql version and use createGraphQLClient from shared package

* Update urql version and use createGraphQLClient from shared package - data importer

* Update urql version and use createGraphQLClient from shared package - cms

* Update CRM

* Update invoices

* Update klaviyo

* Update slack

* Update products feed

* Update search

* Remove unused urql next

* Update monitoring

* Update taxes

* Remove multipart since no longer used

* Update the lockfile

* Removed urql introspection since none of our apps used it

* Add changeset
2023-06-19 15:59:27 +02:00
..
blue-lies-enjoy.md feat: redesign taxes app with macaw-ui (#433) 2023-06-15 09:01:50 +02:00
blue-wasps-cover.md Add logo to apps (#552) 2023-06-14 16:05:36 +02:00
cold-candles-fly.md fix: QA bugs in Taxes App (#654) 2023-06-19 12:06:05 +02:00
config.json Setup changesets 2023-02-07 19:40:59 +01:00
eight-toes-kneel.md feat: redesign taxes app with macaw-ui (#433) 2023-06-15 09:01:50 +02:00
few-boxes-doubt.md feat: redesign taxes app with macaw-ui (#433) 2023-06-15 09:01:50 +02:00
lemon-maps-grow.md Add logo to apps (#552) 2023-06-14 16:05:36 +02:00
poor-chairs-reflect.md Unify urql version, use shared util to create client (#657) 2023-06-19 15:59:27 +02:00
README.md Update README.md (#649) 2023-06-16 09:06:41 +02:00
spicy-seahorses-shake.md Update dependencies (#568) 2023-06-15 08:18:54 +02:00
stupid-insects-smash.md Unify urql version, use shared util to create client (#657) 2023-06-19 15:59:27 +02:00
tricky-rings-beam.md Changed index prefix in algolia to be optional (#553) 2023-06-13 13:37:17 +02:00
young-tigers-provide.md 📧 Improve SMTP event section (#548) 2023-06-15 10:52:39 +02:00

README.md

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 that’s 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 don’t 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