We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This sentence is repeated on both hooks related documentation sections:
fastJoin is preferred over using populate
But I didn't find any link or explanation about why.
So I am asking: why? 🙂
The text was updated successfully, but these errors were encountered:
I am asking because I consider populate more "easier to use" than fastJoin. We can have the related data with just some configuration lines:
populate
fastJoin
I used fastJoin to calculate a price of a record:
fastJoin( { joins: { totalPrice: () => async (ride) => { ride.totalPrice = getTotalPrice(ride.price); }, }, }, ),
This works, but you will certainly say I should use alterItem for that.
alterItem
Plus, you show alterItem example on the documentation to load something that looks like a relation:
alterItems(rec => { rec.userRecord = (async () => await service.get(...) )() })
Well, I am pretty confused. 🙃
I hope you may clarify this. 👍
Sorry, something went wrong.
No branches or pull requests
This sentence is repeated on both hooks related documentation sections:
But I didn't find any link or explanation about why.
So I am asking: why? 🙂
The text was updated successfully, but these errors were encountered: