#Application Logic

1 messages · Page 1 of 1 (latest)

urban thicket
#

This method works perfectly fine, but i seem to be at a roadblock to allow deeper configuration while still being efficient (eg: a workaround would to just be fetching all fields on all routes even those which dont require that information)

I would like to implement further configuration for the session cookie implementation, where certain fields can be fetched predeterminedly depending on the route, by specifying something within the middleware or extractor

#

Ive thought about approaches such as setting something within the extensions BEFORE the middleware/extractor, like a struct that has boolean values to specify what fields to fetch, but that approach seems unintuitive and clunky