Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump ember-cli-mirage from 0.3.4 to 0.4.7 #409

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link

Bumps ember-cli-mirage from 0.3.4 to 0.4.7.

Release notes

Sourced from ember-cli-mirage's releases.

v0.4.7

  • Better console log messages. Console messages are grouped, and now show request and response.
  • Better association() helper. The association() helper used in Factories will no longer create a belongsTo association if one is being passed in at the time of creation.
  • Adds .none() method to Collections.
  • Bugfix: polymorphic relationships.
  • Bugfix: smarter data linkage when including by query params.

v0.4.6

Server routes (server.post('foo')) now return pretender handlers. https://github-redirect.dependabot.com/samselikoff/ember-cli-mirage/pull/1309

v0.4.5

Fix a bug that came up when using Mirage in addons: Attempting to watch missing directory

v0.4.4

v0.4.3

  • Improve detection of model inverses
  • Fix a bug related to serializing responsese that are both sideloaded and embedded

v0.4.2

  • Adds support for new style (RFC232/RFC268) tests
  • Parts of Mirage's factory layer that create data are faster
  • Serializers support coalesced IDs
  • Ensure JSONAPISerializer supports include as function
  • Add support for options mocking

How it works in different types of tests

  • Old-style non-acceptance tests: mirage will not automatically start, and can still be manually started using the startMirage() import from <app>/initializers/ember-cli-mirage.
  • Old-style acceptance tests: mirage will still be started before each test by <app>/initializers/ember-cli-mirage and shut down by the code that ember-cli-mirage's blueprint adds to destroyApp().
  • RFC232 and RFC268 tests: <app>/initializers/ember-cli-mirage will detect that it's an RFC232/RFC268 test and not start the mirage server automatically in the way that is problematic for the new tests, and since the new tests don't use destroyApp(), it's not at play either. So there are two options:
    • In each test that needs it, call setupMirageTest(), which will register beforeEach/afterEach hooks to set up and shut down the mirage server and make it accessible via this.server (and also the server global).
    • Set autostart: true in your ember-cli-mirage config object in config/environment which will cause an instance initializer to run before each test (every RFC232/RFC268 test, not just "acceptance" (application) tests) to start mirage and set it as this.server on the test context (and also the server global), and also register and create a singleton that, when destroyed during app shutdown, will shut down the mirage server.

Upgrade path

This is not a breaking change -- existing tests will run just as they are. Furthermore, new and old tests can live side by side and work properly with mirage if the right setup is done, so you are not forced to migrate your whole suite all at once. As you migrate tests, you have two options:

  • As non-acceptance tests are migrated, delete the manual starting/stopping of mirage in beforeEach/afterEach and replace it with a call to setupMirageTest() and continue using this.server. As acceptance tests are migrated, add a call to setupMirageTest() and optionally switch from using the server global to using this.server.
  • Set autostart: true in config/environment, and then as non-acceptance tests are migrated, just delete the manual starting/stopping of the mirage server and continue using this.server. As acceptance tests are migrated, no changes are necessary, but users can optionally switch from using the server global to using this.server.

v0.4.1

Update notes: none

Changes:

  • [BREAKING CHANGE]#1263 Mirage's initializer was renamed from ember-cli-mirage to ember-cli-mirage-config. This was unintentional and has been reverted in master.
  • [BUGFIX]#1217 Make tracking pretender requests configurable after it was hardcoded false #1137. patrickjholloway
... (truncated)
Commits
  • 51ceafb 0.4.7
  • 04966e4 Merge pull request #1319 from samselikoff/1318-fix-linkage-data-bug
  • fd849ca [closes #1318] Fix linkage data bug
  • e3023d1 Merge pull request #1315 from happycollision/issue-1298
  • b5dc6cd Merge pull request #1311 from gcollazo/enhance-log-messages
  • af5bbc8 Merge pull request #1290 from mehulkar/schema-none
  • 65e844a Do not create an association if one is passed in as an override
  • 5cc5de8 Create failing test for issue #1298
  • e0391fb Merge pull request #1312 from yapplabs/bug/polymorphic-belongs-to
  • 451dc6a Fixup test
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use (this|these) label[s] will set the current labels as the default for future PRs for this repo and language
  • @dependabot use (this|these) reviewer[s] will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use (this|these) assignee[s] will set the current assignees as the default for future PRs for this repo and language

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant