@bagaar/ember-graphql-mocking 0.3.0 → 0.4.1

package/CHANGELOG.md

@@ -1,5 +1,38 @@
 
-## v0.3.0 (2022-02-02)
+
+
+## v0.4.1 (2022-02-09)
+
+#### :bug: Bug Fix
+* [#24](https://github.com/Bagaar/ember-graphql-mocking/pull/24) Don't automatically stop the worker when all tests are done (fix compat with `ember-cli-code-coverage@v1`) ([@bertdeblock](https://github.com/bertdeblock))
+
+#### :memo: Documentation
+* [#19](https://github.com/Bagaar/ember-graphql-mocking/pull/19) Fix install command in docs ([@bertdeblock](https://github.com/bertdeblock))
+
+#### :house: Internal
+* [#22](https://github.com/Bagaar/ember-graphql-mocking/pull/22) Don't publish `.husky` folder and `RELEASE.md` file ([@bertdeblock](https://github.com/bertdeblock))
+
+#### Committers: 1
+- Bert De Block ([@bertdeblock](https://github.com/bertdeblock))
+
+## v0.4.0 (2022-02-03)
+
+#### :rocket: Enhancement
+* [#18](https://github.com/Bagaar/ember-graphql-mocking/pull/18) Make `msw` start options configurable ([@bertdeblock](https://github.com/bertdeblock))
+
+#### Committers: 1
+- Bert De Block ([@bertdeblock](https://github.com/bertdeblock))
+
+## v0.3.2 (2022-02-02)
+
+#### :house: Internal
+* [#17](https://github.com/Bagaar/ember-graphql-mocking/pull/17) Fix release commit message ([@bertdeblock](https://github.com/bertdeblock))
+
+#### Committers: 1
+- Bert De Block ([@bertdeblock](https://github.com/bertdeblock))
+
+
+## v0.3.1 (2022-02-02)
 
 #### :house: Internal
 * [#16](https://github.com/Bagaar/ember-graphql-mocking/pull/16) Update publish config ([@bertdeblock](https://github.com/bertdeblock))

package/README.md

@@ -17,7 +17,7 @@ Ember addon for mocking GraphQL requests using [Mock Service Worker (MSW)](https
 ## Installation
 
 ```shell
-ember install bagaar/ember-graphql-mocking#v0.1.1
+ember install @bagaar/ember-graphql-mocking
 ```
 
 ## Usage

package/addon-test-support/index.js

@@ -1,12 +1,18 @@
 import { assert } from '@ember/debug';
 import { buildASTSchema, graphql } from 'graphql';
+import merge from 'lodash.merge';
 import { graphql as mswGraphql, setupWorker } from 'msw';
-import { done as qunitDone } from 'qunit';
 
 const IS_TESTEM = Boolean(window.Testem);
 const DEFAULT_OPTIONS = {
-  quiet: IS_TESTEM,
-  scope: IS_TESTEM ? window.location.pathname : '/tests',
+  mswStartOptions: {
+    quiet: IS_TESTEM,
+    serviceWorker: {
+      options: {
+        scope: IS_TESTEM ? window.location.pathname : '/tests',
+      },
+    },
+  },
 };
 
 let isSetupGraphqlTestCalled = false;
@@ -14,14 +20,10 @@ let root = null;
 let worker = null;
 
 export function setupEmberGraphqlMocking(schemaDocument, providedOptions) {
-  const options = {
-    ...DEFAULT_OPTIONS,
-    ...providedOptions,
-  };
+  const options = merge({}, DEFAULT_OPTIONS, providedOptions);
 
   createWorker(options);
   createGraphqlOperationHandler(schemaDocument);
-  qunitDone(destroyWorker);
 }
 
 export function setupGraphqlTest(hooks) {
@@ -43,22 +45,16 @@ export function getWorker() {
   return worker;
 }
 
-function createWorker(options) {
-  worker = setupWorker();
+export function destroyWorker() {
+  worker.stop();
 
-  worker.start({
-    quiet: options.quiet,
-    serviceWorker: {
-      options: {
-        scope: options.scope,
-      },
-    },
-  });
+  worker = null;
 }
 
-function destroyWorker() {
-  worker.stop();
-  worker = null;
+function createWorker(options) {
+  worker = setupWorker();
+
+  worker.start(options.mswStartOptions);
 }
 
 function createGraphqlOperationHandler(schemaDocument) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bagaar/ember-graphql-mocking",
-  "version": "0.3.0",
+  "version": "0.4.1",
   "description": "Ember addon for mocking GraphQL requests using Mock Service Worker (MSW).",
   "keywords": [
     "ember-addon"
@@ -37,8 +37,8 @@
     "ember-auto-import": "^2.2.4",
     "ember-cli-babel": "^7.26.11",
     "graphql": "^16.3.0",
-    "msw": "0.36.7",
-    "qunit": "^2.17.2"
+    "lodash.merge": "^4.6.2",
+    "msw": "0.36.7"
   },
   "devDependencies": {
     "@commitlint/cli": "^16.1.0",
@@ -78,6 +78,7 @@
     "loader.js": "^4.7.0",
     "npm-run-all": "^4.1.5",
     "prettier": "^2.5.1",
+    "qunit": "^2.17.2",
     "qunit-dom": "^2.0.0",
     "release-it": "^14.2.1",
     "release-it-lerna-changelog": "^4.0.1",
@@ -107,6 +108,7 @@
       }
     },
     "git": {
+      "commitMessage": "chore(release): ${version}",
       "tagName": "v${version}"
     },
     "github": {

package/.husky/commit-msg

@@ -1,4 +0,0 @@
-#!/bin/sh
-. "$(dirname "$0")/_/husky.sh"
-
-./node_modules/.bin/commitlint --edit "$1"

package/RELEASE.md

@@ -1,60 +0,0 @@
-# Release Process
-
-Releases are mostly automated using
-[release-it](https://github.com/release-it/release-it/) and
-[lerna-changelog](https://github.com/lerna/lerna-changelog/).
-
-## Preparation
-
-Since the majority of the actual release process is automated, the primary
-remaining task prior to releasing is confirming that all pull requests that
-have been merged since the last release have been labeled with the appropriate
-`lerna-changelog` labels and the titles have been updated to ensure they
-represent something that would make sense to our users. Some great information
-on why this is important can be found at
-[keepachangelog.com](https://keepachangelog.com/en/1.0.0/), but the overall
-guiding principle here is that changelogs are for humans, not machines.
-
-When reviewing merged PR's the labels to be used are:
-
-* breaking - Used when the PR is considered a breaking change.
-* enhancement - Used when the PR adds a new feature or enhancement.
-* bug - Used when the PR fixes a bug included in a previous release.
-* documentation - Used when the PR adds or updates documentation.
-* internal - Used for internal changes that still require a mention in the
-  changelog/release notes.
-
-## Release
-
-Once the prep work is completed, the actual release is straight forward:
-
-* First, ensure that you have installed your projects dependencies:
-
-```sh
-yarn install
-```
-
-* Second, ensure that you have obtained a
-  [GitHub personal access token][generate-token] with the `repo` scope (no
-  other permissions are needed). Make sure the token is available as the
-  `GITHUB_AUTH` environment variable.
-
-  For instance:
-
-  ```bash
-  export GITHUB_AUTH=abc123def456
-  ```
-
-[generate-token]: https://github.com/settings/tokens/new?scopes=repo&description=GITHUB_AUTH+env+variable
-
-* And last (but not least 😁) do your release.
-
-```sh
-npx release-it
-```
-
-[release-it](https://github.com/release-it/release-it/) manages the actual
-release process. It will prompt you to to choose the version number after which
-you will have the chance to hand tweak the changelog to be used (for the
-`CHANGELOG.md` and GitHub release), then `release-it` continues on to tagging,
-pushing the tag and commits, etc.