Closed yujiachen-y closed 6 months ago
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
Name | Link |
---|---|
Latest commit | c21a91c8447baad826953fc976e646689685e947 |
Latest deploy log | https://app.netlify.com/sites/casbin/deploys/65ec0e685498880008fdd40c |
Deploy Preview | https://deploy-preview-236--casbin.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
I think it's better to replace 'SHOULD' by 'MUST'.
In the context of guidelines, recommendations, or requirements, "must" and "should" have distinct levels of obligation or expectation:
Must indicates a requirement, obligation, or something that is mandatory. It's used when there's no room for discretion or deviation from the directive. In legal or formal contexts, "must" signifies an absolute requirement.
Should suggests a recommendation or advice that is strongly encouraged but not mandatory. It implies that there are reasons or benefits to follow the guidance, but it's not an absolute requirement. There may be acceptable reasons or circumstances to deviate from a "should" directive.
So, when you see "must," think of it as a non-negotiable rule, whereas "should" is more of a strong suggestion that allows for some exceptions under certain conditions.