feat: domain-functions #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cart route and components
… in address route and components
|
Ficou muito bom, thanks. Vou deixar o PR como referência de um advanced approach (vou referenciar no readme). Por enquanto vou manter mais simples pra exemplificar pra galera do GB. Vlw pela disponibilidade Guga, o brabo! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just to show how we've been using domain-functions at Seasoned and maybe raise some curiosity.
It gets better as the composition of DFs increase in complex routes.
Another benefit is not having to maintain the types as everything is parsed in runtime and then inferred.
When not inferred and checked in runtime the types could be misleading as code or even the cart fetch response could change.
Feel free to accept or reject this PR. I just wanted to show this architecture ;)