Fix : add requirements, consequences and side effects natspec - issue 26

[Jean-Grimal]

Fixes https://github.com/cantinasec/review-morpho-blue-1/issues/26

I didn't add such comments on AaveV3, AaveV2 and AaveV3Optimizer bundlers withdraw functions because receiver will be removed

[Rubilmax]

Fixes cantinasec/review-morpho-blue-1#26

I didn't add such comments on AaveV3, AaveV2 and AaveV3Optimizer bundlers withdraw functions because receiver will be removed

I don't get it: because receiver parameters are expected to be removed, it is actually expected to add the comment to not forget about transferring received funds?

[Jean-Grimal]

Fixes cantinasec/review-morpho-blue-1#26
I didn't add such comments on AaveV3, AaveV2 and AaveV3Optimizer bundlers withdraw functions because receiver will be removed

I don't get it: because receiver parameters are expected to be removed, it is actually expected to add the comment to not forget about transferring received funds?

Yes I was mistaken. But actually (regarding migration bundlers), withdrawn assets are always supplied on Blue, so should the natspec be the same as other bundler (i.e. Withdrawn assets must be transferred from the Bundler to a receiver) Or a specific one like Withdrawn assets must be supplied on Blue (or no natspec for this) ?

[openzeppelin-code]

Fix : add requirements, consequences and side effects natspec - issue 26

Generated at commit: f4747e3ac6d0096460c138ba040bcdcc02c607fc

🚨 Vulnerabilities Summary

Process	Issues	Results
Contract Inspector	note low critical Total	20 10 1 31
Dependency Checker	Total	0

---

For more details view the full report in OpenZeppelin Code