V 2 #1134

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

Closed

kyle-bradley wants to merge 32 commits into eventflow:develop-v1 from kyle-bradley:v-2

.github/workflows/ci.yml

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -63,19 +63,20 @@ jobs:
  
        - uses: actions/checkout@v3

        - name: Setup .NET

          uses: actions/setup-dotnet@v3

          uses: actions/setup-dotnet@v4

          with:

            dotnet-version:

              3.1.x

              6.0.x

              8.0.x

        # Yes, EventFlow has a custom built build tool. If you are reading this

        # you might have a better idea of how to do it alternatively, if so,

        # create a PR for EventFlow.

        # https://github.com/rasmus/Bake

        - name: Install Bake 

          run: dotnet tool install -g --version 0.20.33-beta Bake

          run: dotnet tool install -g --version 0.23.36-beta Bake

        - name: Run Bake

          run: |

.github/workflows/codeql-analysis.yml

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -28,7 +28,7 @@ jobs:
  
          uses: actions/checkout@v3

        - name: Setup .NET

          uses: actions/setup-dotnet@v3

          uses: actions/setup-dotnet@v4

          with:

            dotnet-version: |

              2.1.x

    @@ -37,12 +37,12 @@ jobs:
  
        # Initializes the CodeQL tools for scanning.

        - name: Initialize CodeQL

          uses: github/codeql-action/init@v2

          uses: github/codeql-action/init@v3

          with:

            languages: ${{ matrix.language }}

        - name: Autobuild

          uses: github/codeql-action/autobuild@v2

          uses: github/codeql-action/autobuild@v3

        # ℹ️ Command-line programs to run using the OS shell.

        # 📚 https://git.io/JvXDl

    @@ -56,4 +56,4 @@ jobs:
  
        #   make release

        - name: Perform CodeQL Analysis

          uses: github/codeql-action/analyze@v2

          uses: github/codeql-action/analyze@v3

.github/workflows/docs.yml

-Original file line number
+Diff line change
@@ Expand Up / @@ -12,7 +12,7 @@ jobs: @@
           contents: write
         steps:
           - uses: actions/checkout@v3
-          - uses: actions/setup-python@v4
+          - uses: actions/setup-python@v5
             with:
               python-version: 3.x
@@ Expand Down @@

.github/workflows/release.yml

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -7,6 +7,10 @@ on:
  
    jobs:

      build:

        runs-on: ubuntu-20.04

        environment: 

          name: release

        env:

          HELPZ_POSTGRESQL_PASS: Password12!

          EVENTFLOW_MSSQL_SERVER: 127.0.0.1,1433

    @@ -63,19 +67,20 @@ jobs:
  
        - uses: actions/checkout@v3

        - name: Setup .NET

          uses: actions/setup-dotnet@v3

          uses: actions/setup-dotnet@v4

          with:

            dotnet-version:

              3.1.x

              6.0.x

              8.0.x

        # Yes, EventFlow has a custom built build tool. If you are reading this

        # you might have a better idea of how to do it alternatively, if so,

        # create a PR for EventFlow.

        # https://github.com/rasmus/Bake

        - name: Install Bake 

          run: dotnet tool install -g --version 0.20.33-beta Bake

          run: dotnet tool install -g --version 0.23.36-beta Bake

        - name: Run Bake

          run: |

.github/workflows/stale.yml

-Original file line number
+Diff line change
@@ Expand Up / @@ -77,4 +77,5 @@ jobs: @@
               stale-pr-label: stale
               stale-issue-label: stale
               exempt-pr-labels: stale-exempt
+              exempt-issue-labels: stale-exempt
               operations-per-run: 1000

Documentation/basics/jobs.md

            
                      Original file line number
                      Diff line number
                      Diff line change
                  
    @@ -5,7 +5,7 @@ parent: Basics
  
    nav_order: 2

    ---

    .. _jobs:

    .. \_jobs:

    # Jobs

    @@ -16,8 +16,8 @@ provides basic functionality for jobs.
  
    There are areas where you might find jobs very useful, here are some

    examples

    -  Publish a command at a specific time in the future

    -  Transient error handling

    - Publish a command at a specific time in the future

    - Transient error handling

    ```csharp

    var jobScheduler = resolver.Resolve<IJobScheduler>();

    @@ -33,17 +33,16 @@ In the above example the `SendEmailCommand` command will be published
  
    in seven days.

    !!! attention

        When working with jobs, you should be aware of the following

    When working with jobs, you should be aware of the following

        - The default implementation does executes the job *now* (completely ignoring `runAt`/`delay` parameters) and in the

          current context. To get support for scheduled jobs, inject another implementation of `IJobScheduler`, 

          current context. To get support for scheduled jobs, inject another implementation of `IJobScheduler`,

          e.g. by  installing ``EventFlow.Hangfire`` (Read below for details).

        - Your jobs should serialize to JSON properly, see the section on

          `value objects <./ValueObjects.md>`__ for more information

        - If you use the provided ``PublishCommandJob``, make sure that your

          commands serialize properly as well

    ## Create your own jobs

    To create your own jobs, your job merely needs to implement the `IJob`

    @@ -77,7 +76,7 @@ version to EventFlow and this is how EventFlow distinguishes between the
  
    different job types. This makes it possible for you to reorder your

    code, even rename the job type. As long as you keep the same attribute

    values it is considered the same job in EventFlow. If the attribute is

    omitted, the name will be the type name and version will be ``1``.

    omitted, the name will be the type name and version will be `1`.

    Here's how the job is registered in EventFlow.

    @@ -102,17 +101,22 @@ await jobScheduler.ScheduleAsync(
  
    ## Hangfire

    To use `Hangfire <http://hangfire.io/>`__ as the job scheduler, install

    the NuGet package ``EventFlow.Hangfire`` and configure EventFlow to use

    To use `Hangfire <http://hangfire.io/>`\_\_ as the job scheduler, install

    the NuGet package `EventFlow.Hangfire` and configure EventFlow to use

    the scheduler like this.

    hangfire supports several different storage solutions including Microsoft SQL Server and MongoDB. Use only inMemoryStorage for testing and development.

    ```csharp

    var resolver = EventFlowOptions.new

      .UseHangfireJobScheduler() // This line

      ...

      .CreateResolver();

    private void RegisterHangfire(IEventFlowOptions eventFlowOptions)

    {

        eventFlowOptions.ServiceCollection

            .AddHangfire(c => c.UseInMemoryStorage())

            .AddHangfireServer();

        eventFlowOptions.UseHangfireJobScheduler();

    }

    ```

    !!! note

        The `UseHangfireJobScheduler()` doesn't do any Hangfire

        configuration, but merely registers the proper scheduler in EventFlow.

    The `UseHangfireJobScheduler()` doesn't do any Hangfire

    configuration, but merely registers the proper scheduler in EventFlow.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

V 2 #1134

Uh oh!

Diff view

Diff view

Uh oh!

There are no files selected for viewing

Uh oh!