Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add support for offline storage of errors to Raygun4Net Core #530

Merged
merged 21 commits into from
Jun 7, 2024
Merged

Add support for offline storage of errors to Raygun4Net Core #530

merged 21 commits into from
Jun 7, 2024

Commits on May 30, 2024

  1. Add support for offline storage of errors to Raygun4Net Core 

    This is an early implementation to allow for early feedback and suggestions
    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    a25db7c View commit details
    Browse the repository at this point in the history

  2. Add overload to ctor

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    1fddfd9 View commit details
    Browse the repository at this point in the history

  3. Fix the serialization issues and restructure the sending of payloads

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    61d25e8 View commit details
    Browse the repository at this point in the history

  4. Bit of a rename and removal of sent reports working with location 

    This needs a little more thinking
    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    9f09a71 View commit details
    Browse the repository at this point in the history

  5. Store a map of locations for removing cache entries 

    Mark failed files
    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    d0b6f7f View commit details
    Browse the repository at this point in the history

  6. Fix tests

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    e1b697e View commit details
    Browse the repository at this point in the history

  7. naming

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    781916a View commit details
    Browse the repository at this point in the history

  8. No cast!

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    0e6ddd1 View commit details
    Browse the repository at this point in the history

  9. Employ a finally block to clean up the logic

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    f34d373 View commit details
    Browse the repository at this point in the history

  10. Move the crash store into a getter/setter property instead of the ctor

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    5b7358c View commit details
    Browse the repository at this point in the history

  11. Rename to store

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    4c4dbda View commit details
    Browse the repository at this point in the history

  12. Move store to settings, and clean up send logic

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    9f4b667 View commit details
    Browse the repository at this point in the history

  13. Flip the processing to the store, move the sending into a strategy. 

    This should encapsulate the background timer logic, but not mess with weird statics.

It ties a store to a send strategy, and that store can be a singleton managed by the user
    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    610d347 View commit details
    Browse the repository at this point in the history

  14. Make interfaces explicit

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    4986a57 View commit details
    Browse the repository at this point in the history

  15. Not everything needs to be an interface!

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    22fea6a View commit details
    Browse the repository at this point in the history

  16. Correct some of the sending logic.

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    cba4c80 View commit details
    Browse the repository at this point in the history

  17. Add boolean to prevent re-saving failed offline errors

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    690c705 View commit details
    Browse the repository at this point in the history

  18. Attempt to fix the env var tests

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    7a8d205 View commit details
    Browse the repository at this point in the history

  19. Reset the last updated on each test

    @xenolightning
    xenolightning committed May 30, 2024
    Configuration menu
    Copy the full SHA
    1ce8541 View commit details
    Browse the repository at this point in the history

Commits on Jun 3, 2024

  1. Add nullables

    @xenolightning
    xenolightning committed Jun 3, 2024
    Configuration menu
    Copy the full SHA
    a7940e0 View commit details
    Browse the repository at this point in the history

Commits on Jun 4, 2024

  1. pr feedbacks

    @xenolightning
    xenolightning committed Jun 4, 2024
    Configuration menu
    Copy the full SHA
    0074dec View commit details
    Browse the repository at this point in the history