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

Update dependency handlebars to version 4.0.8 #194

Merged
merged 2 commits into from
May 3, 2017

Conversation

renovate-bot
Copy link
Collaborator

@renovate-bot renovate-bot commented Apr 29, 2017

This Pull Request updates dependency handlebars from version 4.0.6 to 4.0.8

Changelog

4.0.8 / 2017-05-02

  • Bump version in master-branch to 5.0-alpha.1
    This is in order to make sure that the master-branch version is not
    confused with the stable 4.x
  • Merge branch '4.x' into wycats-master

4.0.7 / 2017-04-29

  • v4.0.7
  • Update release-notes for 4.0.7
  • Merge branch '4.x' into wycats-master

    Conflicts:

    spec/regressions.js

  • Fix context-stack when calling block-helpers on null values
    Fixes #1319
    Original behaviour:
    • When a block-helper was called on a null-context, an empty object was used
      as context instead. (#1093)
    • The runtime verifies that whether the current context equals the
      last context and adds the current context to the stack, if it is not.
      This is done, so that inside a block-helper, the ".." path can be used
      to go back to the parent element.
    • If the helper is called on a "null" element, the context was added, even
      though it shouldn't be, because the "null != {}"
      Fix:
    • The commit replaces "null" by the identifiable "container.nullContext"
      instead of "{}". "nullContext" is a sealed empty object.
    • An additional check in the runtime verifies that the context is
      only added to the stack, if it is not the nullContext.
      Backwards compatibility within 4.0.x-versions:
    • This commit changes the compiler and compiled templates would not work
      with runtime-versions 4.0.0 - 4.0.6, because of the "nullContext"
      property. That's way, the compiled code reads
      "(container.nullContext || {})" so that the behavior will degrade
      gracefully with older runtime versions: Everything else will work
      fine, but Add [skip ci] to pin dependency PR #1319 will still be broken, if you use a newer compiler
      with a pre 4.0.7 runtime.
  • Merge pull request #1325 from robinhouston/pr-whitespace-differences
    Document whitespace compatibility difference with mustache
    Fixes #1324
  • Document whitespace compatibility difference with mustache
  • Merge pull request #1323 from chancancode/patch-1
    Update README to be more accurate
  • Update README to be more accurate
    Copied from the website at @wycats' request.
    Addresses #1119.
  • Merge pull request #1315 from Turbo87/es6-parser
    parser: Change suffix to use ES6 default module export
  • Parser: Change suffix to use ES6 default module export
    • This export will be transpiled by Babel for the cjs distribution,
      but will enable others to use a pure ES6 module distribution
    • Instanbul: Ignore "parser.js" for coverage reporting. This file was ignored before
      via annotation, but this has no effect anymore due to the above change
    • Remove istanbul annotation from `parser-prefix` (@nknapp)
      Squashed by @nknapp
      (cherry picked from commit 508347e)
  • Parser: Change suffix to use ES6 default module export
    • This export will be transpiled by Babel for the cjs distribution,
      but will enable others to use a pure ES6 module distribution
    • Instanbul: Ignore "parser.js" for coverage reporting. This file was ignored before
      via annotation, but this has no effect anymore due to the above change
    • Remove istanbul annotation from `parser-prefix` (@nknapp)
      Squashed by @nknapp
  • Merge pull request #1306 from wycats/merge-4.x
    Merge 4.x into master
  • Merge branch '4.x'

    Conflicts:

    Gruntfile.js

    lib/handlebars/exception.js

    spec/partials.js

    spec/regressions.js

  • Add more tests for partial-blocks and inline partials
    • Multiple partial-blocks at different nesting levels
    • Calling partial-blocks twice with nested partial-blocks
    • Calling the partial-block from within the #each-helper
    • nested inline partials with partial-blocks on different nesting levels
    • nested inline partials (twice at each level)
  • Fix for #1252: Using @partial-block twice in a template not possible
    Fixes #1252
    • This fix treats partial-blocks more like closures and uses the closure-context of
      the "invokePartial"-function to store the @partial-block for the partial.
    • Adds a tes for the fix
  • Avoid duplicate "sourceMappingURL=" lines.
    Avoid duplicate // sourceMappingURL=... lines when minifying AND
    generating a map. UglifyJS2 will write the line when minifying.
    (cherry picked from commit 660a117)
  • Avoid duplicate "sourceMappingURL=" lines.
    Avoid duplicate // sourceMappingURL=... lines when minifying AND
    generating a map. UglifyJS2 will write the line when minifying.
  • Fix compiler-api example (#1303)
    Closes #1302
    While trying to answer #1302, I noticed that the compiler-api example did not work in (because `nameLookup` is actually at the prototype). This example has a jsfiddle that proves it is working.
    It does not provide an solve the exact problem of the reporter, but it answers the question.
  • Moved .eslintrc to .eslintrc.js and cleaned up rules
    Extending from eslint:recommended so we stay up to date on the latest
    recommended rules.
  • Fix README filename in package.json
    There is `README.markdown` in handlebars.js repository, not a `README.md`.
  • add more machine-readable data about the license
    This small change is meant to make LibreJS happy.
    Closes: #1273
  • Added ".editorconfig"-file that specifies the indent for javascript-files (#1292)
  • Eslint upgrade to 19.0.0 and configuration fixes (#1294)
    Original PR by @travnels, commit-message edited by @nknapp
    • Upgraded eslint to 19.0.0
    • Cleaned up duplicate rules 'no-extra-parens', 'quote-props'
    • eslint rule 'no-empty-label' was replaced.
      Rule 'no-empty-label' was removed and replaced by: ‘no-labels’. ‘no-labels’ already in the project
    • eslint rule 'space-after-keywords' has been replaced
      Rules 'space-after-keywords' and 'space-return-throw-case' wer removed and replaced by ‘keyword-spacing’.
    • Added parsoer-option: sourceType='module'
    • Add unnecessary=false to 'quote-props' to remove warnings about unnecessarily quoted property.
      Code corrections
    • helpers.js: unused variable 'depthString' removed, detected by new eslint
  • Fix istanbul dev dependency
    According to npm's documentation[1], dependencies on github
    repositories are declared with the following syntax:
    "module": "person/module"
    This commit changes the package.json syntax on istanbul's dependency,
    to follow the documentation.
    [1] https://docs.npmjs.com/files/package.json#github-urls
  • require('sys') is deprecated, using 'util' instead
    (node:30288) DeprecationWarning: sys is deprecated. Use util instead.
    (cherry picked from commit 9a36966 by @travnels)
  • require('sys') is deprecated, using 'util' instead
    (node:30288) DeprecationWarning: sys is deprecated. Use util instead.
  • Template for issues and pull-request
    I've noticed that many issues are answered with "Please provide a jsfiddle".
    This issue template tells the reporter to do that from the start.
  • Make "column"-property of Errors enumerable
    Fixes #1284
    Appearently, there is a use-case of stringifying the error in order to
    evaluated its properties on another system. There was a regression
    from 4.0.5 to 4.0.6 that the column-property of compilation errors
    was not enumerable anymore in 4.0.6 (due to commit 20c965c) and
    thus was not included in the output of "JSON.stringify".
  • Testcase to verify that compile-errors have a column-property
    Related to #1284
    The test ensures that the property is there, because it is important to
    some people.

@codecov-io
Copy link

codecov-io commented Apr 29, 2017

Codecov Report

Merging #194 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master    #194   +/-   ##
======================================
  Coverage    73.8%   73.8%           
======================================
  Files          19      19           
  Lines        1092    1092           
  Branches      211     211           
======================================
  Hits          806     806           
  Misses        286     286

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf11518...dfd1ac8. Read the comment docs.

@renovate-bot renovate-bot changed the title Update dependency handlebars to version 4.0.7 Update dependency handlebars to version 4.0.8 May 2, 2017
@rarkins rarkins merged commit 94d4537 into master May 3, 2017
@rarkins rarkins deleted the renovate/handlebars-4.x branch May 3, 2017 03:31
@rarkins rarkins removed the ready label May 3, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.