Skip to content

undocumented restrictions, that cause Exceptions at runtime #47

@LukasGelke

Description

@LukasGelke

For example: the re-use of Request/Replies is not possible:
Image

also apparently endpoints have to directly inherit from Endpoint<,>

why did I try this:

  • Endpoints and Handlers are "identified" by EndpointName
  • some Endpoints/Handlers are essentially just void DoAction(object viewModel)
    • then why not use i.e. ViewModelOnlyRequest and VoidResponse/Response.Empty for all of them?

This would be a perfect situation for an accompanying Analyzer. However I understand that due to possible future changes, Analyzers are "potentially more wasted time". However there aren't even DocComments on the relevant base classes. The only thing in the blog post I found was

TemplateAssignmentEditorOKClickResponse: This class doesn’t carry any additional parameter. But it must be there to fullfil the required convention.

which does not talk about re-usability/uniqueness

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions