context 2.0.0-next-9f9b97 → 2.0.0-next-8ba989

package/CHANGELOG.md

@@ -4,13 +4,14 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
-## 2.0.0 - 2021-11-24
+## 2.0.0 - 2021-12-17
 ### Changed or removed
 - 7c43eab  major(context): used named export in context (ealush)
 - e8652bc  breaking(vest, enforce): prepare next major (ealush)
 - dab8e00  breaking(vest, enforce): prepare next major (ealush)
 
 ### Added
+- b0a9a14  feat(vest): use key prop to retain test state after reorder (#732) (Evyatar)
 - 220127b  added(n4s): partial rule modifier (undefined)
 - b5ce72d  feat(n4s): context propagation within enforce (undefined)
 

package/README.md

@@ -4,6 +4,7 @@ Simple utility for context propagation within Javascript applications and librar
 It allows you to keep reference for shared variables, and access them down in your function call even if not declared in the same scope.
 
 ## How Context Works?
+
 The way context works is quite simple. Creating a context initializes a closure with a context storage object. When you run your context call, it takes your values, and places them in the context storage object. When your function finishes running, the context is cleared.
 
 ![image](https://user-images.githubusercontent.com/11255103/137119151-6912d3f1-ab48-4c91-a426-76af8abc8c55.png)
@@ -125,13 +126,15 @@ Working with context inside within async code may lead to unexpected results whe
 This is known and expected behavior. Context is a synchronous context propagation tool that completely relies on the synchronous nature of function calls in JS - this is exactly what allows context to run.
 
 #### But my function is still running. Why did the context clear?
+
 The async parts of your function are actually not executed along with your sync code, and even though you "await" it, the browser carries on and allows other code to run in between instead of blocking execution until your async code is complete.
 
 #### Ok, so what do I do?
+
 There are multiple strategies of handling async functions with context.
 
 1. Pulling your values from context right before your async call
-This is the most obvious and easiest to achieve, though not always what you need. The basic idea is that you take whatever you need from the context when it is still available to you.
+   This is the most obvious and easiest to achieve, though not always what you need. The basic idea is that you take whatever you need from the context when it is still available to you.
 
 2. context.bind or context.run your async function to the context you extracted
-This is the next logical step - you have a function that you know should run later with your context. You can bind your context to it for delayed execution. When your function runs later down the line within your asynchronous code, internally it will still have access to whatever you bound to it.
+   This is the next logical step - you have a function that you know should run later with your context. You can bind your context to it for delayed execution. When your function runs later down the line within your asynchronous code, internally it will still have access to whatever you bound to it.

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.0.0-next-9f9b97",
+  "version": "2.0.0-next-8ba989",
   "license": "MIT",
   "main": "./dist/cjs/context.js",
   "types": "./types/context.d.ts",