Fix flipped/mixed up Expecto.Diff formatting

[lydell]

Fixes https://github.com/haf/expecto/issues/419

I tested this by running dotnet run --project Expecto.Sample --framework net5.0 in this repo.

First, the default output for comparison:

Notes:

• Expected comes first, then actual.
• Expected is in green, actual in red.

Then, the Expecto.Diff output:

Notes:

• The Actual/Expected headings are flipped compared to the default formatting.
• The actual/expected text are still in the same order as the default formatting. In other words, the headings are for the wrong text.
• The colors are flipped compared to the default formatting.
• Also note how the first heading and {A = is blue, while it should be white.

Finally, the output with this PR:

Notes:

• Fixed the headings so Expected comes first, just like in the default formatting. And now the headings and the actual/expected text match.
• Fixed the colors. Expected is now green and actual is red, just like the default formatting.
• Fixed the heading and start-of-text color. It’s now reset.

[lydell]

@haf Friendly ping :) Small change, great quality of life improvement

[haf]

Ah sorry, haven't seen this. Thanks @lydell !

[lydell]

Thanks! What’s the plan for the next release? Is it days, weeks, months? Easier to wait for something good when you’ve got a rough estimate of the time frame 🙏

[olivercoad]

@haf Any chance you could push an update to nuget some time?

[haf]

@olivercoad Just a lot to do every day. Could you help me get this auto-publishing with Github Actions? I'd happily add in secrets and such to the repo so that it can work.

[haf]

I've added the secret NUGET_RELEASE_KEY that we can use to push new nugets on every commit to master. (And let's rename it to main while we're at it!)

[olivercoad]

No worries. Thanks for setting up the secret, I'll try and have a look at how to get auto-publishing working.

[olivercoad]

push new nugets on every commit to master

I'm guessing something like this would do that (looking at https://docs.github.com/en/actions/guides/building-and-testing-net#publishing-to-package-registries)

name: Publish Nuget Packages
on:
  push:
    branches: [ main ]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: Setup .Net
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: "5.0"
      env:
        NUGET_TOKEN: ${{secrets.NUGET_RELEASE_KEY}}
    - run: ./fake build --target Push

Though you'd probably want some kind of manual action so it it only pushes when you change the version number or something.

[baronfel]

you can also do manual job runs, which we do in fsautocomplete:

on:
  workflow_dispatch:
    inputs:
      username:
        description: Github username of the person triggering the release
        default: "baronfel"
        required: true
      email:
        description: Email of the person triggering the release
        default: "some_email@place.com"
        required: true

these can be referenced in subsequent steps, or you can leave them out entirely to require a manual job. in either case only users with write access can trigger them.

[haf]

I'm happy with any solution that gives me more time.

Every time I run ./fake build --target Push that target fails for unspecified reasons and I have to manually push everything with the shell script line that is a comment in the fsx file.

[haf]

I changed the script like you suggested @olivercoad