Thiemo Kreuz b28f48d6d6 Rename variables in change listeners for clarity ... This patch does nothing but rename a pair of variables: "prevState/state" becomes "oldState/newState". Reasoning: 1. The abbreviated "prev" is confusing, especially because we are in a codebase that is all about "previews". 2. We are in a context that is all about a state **change**. Change listeners get notified about the change from one state to another. While it would be possible to stick to the already mentioned "previous/current" terminology, I find the word "current" confusing. What is "current" in this context? Did the state already change? Am I notified about a change that is **going** to happen or already happened? Is this even relevant? I don't think it is. Therefor "old/new". Another possibility is "previous/next". Change-Id: Id886e1a095967fe86fb9021f59e335c62da8994e		2021-04-15 10:19:40 +02:00
..
adr	Hygiene: rename NPM test:node to test:unit	2019-01-24 08:29:27 -07:00
images/instrumentation
change_listener.md	Rename variables in change listeners for clarity	2021-04-15 10:19:40 +02:00
instrumentation.md	Fiy a few small typos in the Popups documentation	2018-12-11 18:23:30 +01:00