Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: junaozun/otto Loading
base: master
Choose a base ref
...
head repository: robertkrimen/otto Loading
compare: master
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 5 commits
  • 75 files changed
  • 5 contributors

Commits on Apr 13, 2024

  1. chore: update ci versions (robertkrimen#519)

    Update go, golangci-lint and action versions.
    
    Address new lint failures flagged by updated golangci-lint version.
    stevenh committed Apr 13, 2024
    Configuration menu
    Copy the full SHA
    98effe0 View commit details
    Browse the repository at this point in the history
  2. feat: support Object.values() (robertkrimen#518)

    Adds support for `Object.values()`
    rorymalcolm committed Apr 13, 2024
    Configuration menu
    Copy the full SHA
    1ca7723 View commit details
    Browse the repository at this point in the history

Commits on May 3, 2024

  1. feat: support trailing comma after the last argument (robertkrimen#520)

    Add support for trailing comma after the last argument of a method call.
    linuxerwang committed May 3, 2024
    Configuration menu
    Copy the full SHA
    2d23528 View commit details
    Browse the repository at this point in the history

Commits on Jun 12, 2024

  1. fix(parser/lexer): ID_Start & ID_Continue checks (robertkrimen#524)

    Fix the checks for ID_Start & ID_Continue to match the definitions in
    https://www.unicode.org/reports/tr31/
    filips committed Jun 12, 2024
    Configuration menu
    Copy the full SHA
    d4edd51 View commit details
    Browse the repository at this point in the history

Commits on Jul 9, 2024

  1. Fix missing flag from regex literal in corner case (robertkrimen#529)

    In the specific corner case where a regex contains a flag but is not
    followed by any symbols, the ast.RegExpLiteral.Literal value would drop
    (part of) that flag.
    
    This happens because the p.next() call during the parsing of the flag
    wouldn't actually advance the p.chrOffset, and thus endOffset would be
    erroneously adjusted.
    
    The fix is just to use the current p.chrOffset and then call p.next()
    afterwards.
    psve committed Jul 9, 2024
    Configuration menu
    Copy the full SHA
    a39e65d View commit details
    Browse the repository at this point in the history
Loading