-
Notifications
You must be signed in to change notification settings - Fork 0
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: unit improvements #13
Merged
Merged
Changes from all commits
Commits
Show all changes
33 commits
Select commit
Hold shift + click to select a range
b848147
feat: ownable contract and cooldownPeriod setter
gomesalexandre d51c10b
feat: unit improvements
gomesalexandre e666640
feat: all green
gomesalexandre be3480b
feat: more criteria to run CI
gomesalexandre b97fb56
feat: tmp ci monkey patch, revert me when confirmed happy
gomesalexandre 78e9d24
feat: give an actual name to the action
gomesalexandre d9ee5b2
feat: bump foundry version in CI
gomesalexandre 25ff298
chore: trigger CI
gomesalexandre b4d70f9
feat: remove monkey patch
gomesalexandre ca5d7a4
feat: coverage report in CI
gomesalexandre 7c28a4c
feat: emit event including old address
gomesalexandre 41093b6
feat: assume 43-bytes-length RUNE addy
gomesalexandre c43d486
feat: bring back CI monkey patch
gomesalexandre 8f7d02c
feat: make it 100% again
gomesalexandre bfa67d6
feat: remove CI monkey patch
gomesalexandre 2556c8e
feat: add .git-blame-ignore-revs
gomesalexandre 02a9faf
feat: bring back monkey
gomesalexandre 9ef1c87
feat: use zgosalvez/github-actions-report-lcov@v3 in CI
gomesalexandre 44f2715
feat: monkey patch non-100% coverage
gomesalexandre 181a7d3
fix: syntax
gomesalexandre 470a1f6
feat: correct lcov.info loc
gomesalexandre abebf03
feat: use github-actions-report-lcov latest
gomesalexandre da55209
feat: upload and download lcov report
gomesalexandre 91b2cde
feat: foudry as working dir
gomesalexandre 8f7fbf6
feat: attempt 2
gomesalexandre 1eaf228
feat: last attempt
gomesalexandre e5e112f
feat: rage quit
gomesalexandre 1933c1b
fix: rebase issues
woodenfurniture 3365d89
chore: lint
gomesalexandre 4baa74e
feat: lint config
gomesalexandre beec29c
feat: actually lint
gomesalexandre 630e5e9
feat: blame ignore rev
gomesalexandre 476030f
fix: rebase issues
woodenfurniture File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Initial linting | ||
1696c504527d64d9b22cefe03e38ac1f41c90268 |
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
{ | ||
"plugins": ["prettier-plugin-solidity"], | ||
"overrides": [ | ||
{ | ||
"files": "*.sol", | ||
"options": { | ||
"parser": "solidity-parse", | ||
"printWidth": 80, | ||
"tabWidth": 4, | ||
"useTabs": false, | ||
"singleQuote": false, | ||
"bracketSpacing": false | ||
} | ||
} | ||
] | ||
} |
This file was deleted.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
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.
Note this doesn't exit 1 on non-100% coverage unfortunately. Since the output:
is more than likely to stay pretty much the same as we're not going to add more contract files/test files, do we want to have some smallish awk/sed/grep script here to exit 1 on non-100% coverage so that CI can fail? e.g something like this (ChatGPT-generated, untested but the idea is to rely on the output being consistent, filter out the irrelevant lines, and ensure both
FoxStaking
,FoxStaking.t
andTotal
lines are 100.00%.Alternatively,
forge coverage
can output lcov which we may be able to use insteadThere 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.
Re: Using lcov to fail CI on non-100% :sad: :
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.
We'll likely have more files as our test suites expand, but simply checking the total should be totally sufficient.
Could easily have a brute force check of the test with a regex to assert that any number preceding a
%
symbol is the string100.00
, which would cover all files regardless of how many we add in the future