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: dispatch/reboot
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: dispatch/reboot
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.0.x
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 13 commits
  • 6 files changed
  • 3 contributors

Commits on Oct 20, 2018

  1. Configuration menu
    Copy the full SHA
    f575941 View commit details
    Browse the repository at this point in the history

Commits on Nov 4, 2018

  1. Configuration menu
    Copy the full SHA
    016ddea View commit details
    Browse the repository at this point in the history
  2. Merge pull request #207 from dispatch/1.0/realm-with-scheme

    [1.0] Allow to set scheme in as keyword
    farmdawgnation authored Nov 4, 2018
    Configuration menu
    Copy the full SHA
    6687f2a View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    fcff70d View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    c78caf0 View commit details
    Browse the repository at this point in the history

Commits on Oct 5, 2019

  1. Configuration menu
    Copy the full SHA
    802eac1 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    1461932 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    0e4eb5d View commit details
    Browse the repository at this point in the history

Commits on Dec 27, 2019

  1. Correctly url encode emoji in path segments

    The previous implementation borked on emoji because invoking
    char.toString on a single UTF-8 part of a larger UTF-16 pair results in
    the encoding presenting "?" as the value.
    
    This implementation works primarily on Bytes and avoids having to invoke
    char.toString and therefore is capable of correctly encoding emoji
    characters into a UTF-8 url encoded path segment.
    
    This did involve re-working some of the valid character detection for
    path segments, so there is likely a delta to the overall performance,
    but I think it should be negligible.
    farmdawgnation committed Dec 27, 2019
    Configuration menu
    Copy the full SHA
    a3e46a2 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    c62507e View commit details
    Browse the repository at this point in the history
  3. Merge pull request #227 from dispatch/1.0/encode-emoji

    [1.0.x] Correctly url encode emoji in path segments
    farmdawgnation authored Dec 27, 2019
    Configuration menu
    Copy the full SHA
    58e4344 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    b43e103 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    5dd068a View commit details
    Browse the repository at this point in the history
Loading