Skip to content

Routing #552

Closed
Closed
@georeith

Description

@georeith

The problem I am facing

We have multiple types of document with different data in them that have different middleware requirements.

The solution I would like

The ability to set up different middleware routes based on the HTTP path of the original request, query parameters etc.

Alternatives I have considered

Running separate HocusPocus instances for each document type. We do this in some places but this puts more strain on the rest of our deployment infrastructure and is less flexible for taking advantage of our existing resources.

Branching inside middleware blocks but its messy and error prone, everything constantly has to filter the type of document before it can do anything with it.

Additional context

There's some thought to be had around how this would work with multiplexing and subdocuments as they are likely to be documents of different types and may have different storage needs etc.

Some of our views have access to documents of multiple types and it would be nice if they can benefit from multiplexing also.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions