Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance implications of using the filters API? #53

Open
saurabhnanda opened this issue Jan 30, 2024 · 0 comments
Open

Performance implications of using the filters API? #53

saurabhnanda opened this issue Jan 30, 2024 · 0 comments

Comments

@saurabhnanda
Copy link

I want to use filters which operate on complete object, such as:

orderSummary :: Order -> Text

This forces me to define an Unqote instance for the Order type, which (as per my understanding) is a Aeson.Value -> Order parsing step. Does this mean that each of the following call sites is going to parse Aeson.Value -> Order?

{{ order | orderSummary }}
{{ order | orderTotal }}
{{ order | shippingAddress }}

Is there a faster/performant way of doing this? Instead of filters, should I make these available as template-snippets that can be included via a custom resolver?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant