-
Notifications
You must be signed in to change notification settings - Fork 49
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
feat: shape name in create lockup #1094
Conversation
c121ee9
to
ae77c12
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, left some comments below:
I did not fuzz shape names in Fork and Invariant tests since its only emitted in event. So, concrete tests and fuzz tests are sufficient imo
agree that we don't need to fuzz this in fork/invariants (it would be superfluous)
test/integration/concrete/lockup-base/create-with-timestamps/createWithTimestamps.t.sol
Outdated
Show resolved
Hide resolved
docs: uses assertive comments in natspecs test: makes default shape name with non-zero length Co-authored-by: andreivladbrg <andreivladbrg@gmail.com>
Thanks for the review @andreivladbrg. I have incorporated all your suggestions except one. Let me know what you think about that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, 32 bytes is not enough to prevent HTML injection. From ChatGPT convo:
<img src=x onerror=alert(1)>
I think we just have to accept the potential risk and sanitize the shape string at the UI level, cc @sablier-labs/frontend.
Closes #1086.
Changelog
shape
and notshapeName
as I suppose the "name" keyword is implicit given that its astring
type