Per-route custom contexts #6

New Issue

Jef Roosens · 2024-02-08T15:26:41+01:00

Jef Roosens commented

2024-02-08 15:26:41 +01:00

The current design requires defining a single custom route format that's used for all routes. Usually separate types of routes however do not require the same kinds of contexts; some routes don't even need a custom context at all.

A better design might be to define the context callbacks on a per-route level instead of globally, allowing the user to specify as many types of contexts as needed. This would also simplify the reset functions, as they no longer need to account for all the various parts of an agglomerated custom context.

The current design requires defining a single custom route format that's used for all routes. Usually separate types of routes however do not require the same kinds of contexts; some routes don't even need a custom context at all. A better design might be to define the context callbacks on a per-route level instead of globally, allowing the user to specify as many types of contexts as needed. This would also simplify the reset functions, as they no longer need to account for all the various parts of an agglomerated custom context.

Jef Roosens added the

enhancement

label 2024-02-08 15:26:49 +01:00

Sign in to join this conversation.