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

[Snyk] Upgrade @dojo/framework from 6.0.0 to 6.0.3 #3

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

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade @dojo/framework from 6.0.0 to 6.0.3.

  • The recommended version is 3 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2019-09-24.
Release notes
  • Package name: @dojo/framework
    • 6.0.3 - 2019-09-24

      6.0.3

    • 6.0.2 - 2019-09-13

      6.0.2

    • 6.0.1 - 2019-09-12

      6.0.1

    • 6.0.0 - 2019-08-26

      The Dojo framework 6.0.0 release.

      Breaking Changes

      • Merge widget-core with core(#357)
      • Move has to core(#361)
      • Move core functionality to vdom module(#360)
      • Do not throw testing unregistered has flags by default(#278)
      • Stop decorating VNode and WNodes during vdom rendering(#290)
      • Auto bind all class functions(#290, #348)
      • Upgrade minimum TypeScript version to 3.4.5(#331)
      • Error for selectors that cannot be found with assertion templates(#364)
      • Add start method to router(#402)
      • Support factory functions for children replace on assertion templates(#413)
      • Make css transition strategy optional(#418)
      • Throw an error on missing selector in harness trigger(#320)

      Enhancements

      • function-based widgets and middleware support(#352, #451)
      • Core destroy and node middleware(#362)
      • cache middleware(#373)
      • registry middleware(#376)
      • defer middleware(#378)
      • injector middleware(#377)
      • cache middleware(#381, #467, #493)
      • block middleware(#380)
      • resize middleware(#384)
      • diffProperty middleware(#382, #398)
      • theme middleware(#392)
      • dimensions middleware(#388)
      • i18n middleware(#390)
      • focus middleware(#389)
      • store middleware(#391)
      • breakpoint middleware(#387)
      • validity middleware](#452)
      • Support integer like index keys in dojo/stores(#262)
      • Validation Meta(#264)
      • Pluggable state provider for dojo/stores(#242)
      • Pause rendering during merge for lazy loaded widgets(#312)
      • Enable mocking shim'd fetch and web platform polyfills(#295)
      • Allow direct manipulation of dojo/stores state for evergreen browsers()
      • Improved rendering algorithm when all the previous node have been replaced(#356)
      • Convert dojo/shims to also work as polyfills(#347)
      • Pass process id to dojo/store's before callbacks(#409)
      • Harness support for function-based widgets and middleware(#411)
      • Assertion template enhancements(#412)
      • Convert routing widgets to function-based widgets(#414)
      • special virtual tag support(#425)
      • special body tag support(#448, #460, #463)
      • mock store middleware(#428)
      • mock breakpoint middleware(#471)
      • mock resize and intersection middleware(#411)
      • globalThis shim support(#437, #474)
      • Automatically detect children type for custom elements(#502)

      Bug Fixes

      • Disconnect resize meta when destroyed(#272)
      • Ensure nodes are inserted in the correct position when nested within widgets(#297)
      • Stop extending WidgetProperties(#305)
      • Use the latest wrapper when processing detached nodes(#311)
      • Skip changing route for the same url(#317)
      • Do not reuse text node when content is different during merge(#355)
      • Support widgets with typed children in the harness(#365)
      • Ensure shims are elided correctly(#401)
  • from @dojo/framework GitHub release notes
------------

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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

Successfully merging this pull request may close these issues.

1 participant