Skip to content

Provide non-async overload to RespondWith #12

@TheRealPiotrP

Description

@TheRealPiotrP

Current implementation forces async, which will result in warning:
file: 'file://foo.cs'
severity: 'Warning'
message: 'This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread. [Project]'
at: '338,73'
source: ''

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions