vat-moss.js Bump handlebars from 4.0.11 to 4.7.7

Bumps handlebars from 4.0.11 to 4.7.7.

Changelog

v4.7.7 - February 15th, 2021

fix weird error in integration tests - eb860c0

fix: check prototype property access in strict-mode (#1736) - b6d3de7

fix: escape property names in compat mode (#1736) - f058970

refactor: In spec tests, use expectTemplate over equals and shouldThrow (#1683) - 77825f8

chore: start testing on Node.js 12 and 13 - 3789a30

(POSSIBLY) BREAKING CHANGES:

the changes from version 4.6.0 now also apply in when using the compile-option "strict: true". Access to prototype properties is forbidden completely by default, specific properties or methods can be allowed via runtime-options. See #1633 for details. If you are using Handlebars as documented, you should not be accessing prototype properties from your template anyway, so the changes should not be a problem for you. Only the use of undocumented features can break your build.

That is why we only bump the patch version despite mentioning breaking changes.

Commits

v4.7.6 - April 3rd, 2020

Chore/Housekeeping:

#1672 - Switch cmd parser to latest minimist (@dougwilson

Compatibility notes:

Restored Node.js compatibility

Commits

v4.7.5 - April 2nd, 2020

Chore/Housekeeping:

~~Node.js version support has been changed to v6+~~ Reverted in 4.7.6

Compatibility notes:

~~Node.js < v6 is no longer supported~~ Reverted in 4.7.6

Commits

v4.7.4 - April 1st, 2020

Chore/Housekeeping:

#1666 - Replaced minimist with yargs for handlebars CLI (@aorinevo, @AviVahl & @fabb)

Compatibility notes:

... (truncated)

Commits

a9a8e40 v4.7.7
e66aed5 Update release notes
7d4d170 disable IE in Saucelabs tests
eb860c0 fix weird error in integration tests
b6d3de7 fix: check prototype property access in strict-mode (#1736)
f058970 fix: escape property names in compat mode (#1736)
77825f8 refator: In spec tests, use expectTemplate over equals and shouldThrow (#1683)
3789a30 chore: start testing on Node.js 12 and 13
e6ad93e v4.7.6
2bf4fc6 Update release notes
Additional commits viewable in compare view

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 recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor 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 these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

May 07 '21 10:05 dependabot[bot]

@wbond: I know you're busy with all the package control stuff for ST3, but have you had a chance to look at this yet?

Mar 28 '13 23:03 vanrijn

I really like the idea from https://github.com/wbond/sublime_alignment/issues/27 so I modified my code to allow sublime_alignment to do all 3 of the following:

   // This plugin can align the selected lines in a number of ways.
   //   background-color: black;
   //   color:            white;
   // "alignment_format": "key-separator-varspace-value"

   // ... or ...
   //   background-color: black;
   //              color: white;
   // "alignment_format": "varspace-key-separator-value"

   // ... or the default ...
   //   background-color: black;
   //   color           : white;
   "alignment_format": "key-varspace-separator-value"

Apr 12 '13 22:04 vanrijn

Looks good - going to be handy :-)

Apr 13 '13 21:04 GaryJones

Please merge this

Apr 24 '13 14:04 coderberry

I like the change, but...is it hard to make both situations work? I use:

h1 span {
    display:          block;
    font-family:      'weblysleek_uisemilight',sans-serif,Arial;
    font-size:        22px;
    font-weight:      400;
    margin-top:       15px;
}

and for JS:

var test              = 23132
,    longvariable     = 343
,    e                = 3434
;

Unfortunately I cannot use both options at the same time. Is it possible that it will do the key/value alignment based on key-separator-varspace-value and the equals value based on key-varspace-separator-value?

Aug 22 '13 08:08 mattiLeBlanc

Let's get this merged.

Sep 18 '13 05:09 ericmagnuson

@eric, you mean you can make this work? That would be awesome

Sep 18 '13 09:09 mattiLeBlanc

Well, at the time, I was just showing that there was still interest in this pull.

However, since writing that, I forked this repo and pulled in a number of the currently pending pull requests, including this one. It works fairly well I'd say. You should be able to have two different alignment options by editing Javascript.sublime-settings and CSS.sublime-settings, which can be found in the package's folder.

Sep 18 '13 09:09 ericmagnuson

I have set the the javascript.sublime-settings as: { "alignment_chars": ["=", ":"] } But i notice that if I use = or : alignment in a JS file, it doesn't align as the example of mine above. Maybe i made a configuration error.

But in CSS it is mid aligning the : which I do not want, in JS it is mid-aligning the = which is good, but it is also mid-aligning the : which I would not like

Sep 18 '13 10:09 mattiLeBlanc

Hmm, I couldn't get it to work either. I'll have to see if I can figure out why.

Sep 18 '13 20:09 ericmagnuson

Glad you had the same result

Sep 20 '13 08:09 mattiLeBlanc

:+1: on getting this into the main project. I hacked together essentially the same solution for my own needs, but would love to see this get in. How can I help?

Nov 25 '13 18:11 kerrizor

:+1: Except alignment_format should be for each alignment_char

"alignment_chars": [
  "=": "key-varspace-separator-value",
  ":":  "key-separator-varspace-value"
]

//or

"alignment_chars": [
  {
    "char": "=",
    "format": "key-varspace-separator-value"
  },
  {
    "char": ":",
    "format": "key-separator-varspace-value"
  },
]

Sep 04 '14 19:09 James1x0

:+1: I would love to see this being merged in the near future.

Sep 08 '14 09:09 fnky

+1

Apr 23 '15 20:04 danillos

:+1: for merge, please!

May 28 '15 10:05 ArmorDarks

please make it real :) ! :+1:

btw: how about that?

"alignment_types": {
  "key-varspace-separator-value": ['=', '-', '+', '.'],
  "key-separator-varspace-value": [':']
}

Mar 10 '16 11:03 DoubleU23

Any news on this?

Sep 14 '16 10:09 smartforcedev

vat-moss.js vat-moss.js copied to clipboard

Bump handlebars from 4.0.11 to 4.7.7

v4.7.7 - February 15th, 2021

v4.7.6 - April 3rd, 2020

v4.7.5 - April 2nd, 2020

v4.7.4 - April 1st, 2020

vat-moss.js
vat-moss.js copied to clipboard