Closed rndquu closed 4 months ago
not optimally structured code,
Handling this at https://github.com/ubiquity/ubiquibot/pull/644
As for tests, @whilefoo produced some e2e tests already which I merged in and used a few times before redoing all of the code. I'll certainly make sure to get that back up and running before merging my refactor.
Permit generation skipped because the issue was not closed as completed
@pavlovcik This issue also implied adding 2 workflows: running unit tests and checking test coverage for PRs. You sure we don't need those workflows? I don't think we should close this issue as not planned.
/start
Deadline | Mon, 16 Oct 2023 20:46:24 UTC |
Registered Wallet | 0xCAC0A8cF4cc7073b040c7fe6328Da7f229AF40A6 |
/wallet 0x0000...0000
if you want to update your registered payment wallet address @user.Do you have any updates @PhantomCracker? If you would like to release the bounty back to the DevPool, please comment /stop
Last activity time: Mon Oct 16 2023 18:46:17 GMT+0000 (Coordinated Universal Time)
@PhantomCracker - Releasing the bounty back to dev pool because the allocated duration already ended! Last activity time: Mon Oct 16 2023 18:46:17 GMT+0000 (Coordinated Universal Time)
@rndquu I can have a look if you want, since I've been settings tests in the other repos. However, we did not set the blockage on coverage decrease anywhere yet.
@rndquu I can have a look if you want, since I've been settings tests in the other repos. However, we did not set the blockage on coverage decrease anywhere yet.
I think that anything related to this codebase, unless it's strictly event handler related, is not a good idea to invest into.
That's why we actually removed this codebase from the directory.
As you know we plan to move to using the kernel asap.
@whilefoo how's it coming along to get it deployed?
@rndquu I can have a look if you want, since I've been settings tests in the other repos. However, we did not set the blockage on coverage decrease anywhere yet.
Thank for your endeavour
I think this issue should be closed as "not planned" since we're moving to the plugin oriented architecture
# Issue was not closed as completed. Skipping.
There's a pretty big technical debt in the bot's codebase (lack of unit tests, not optimally structured code, etc...). We can't ship new production builds any more without breaking an existing functionality.
We should setup a unit testing workflow and stop accepting PRs without unit tests and docs. This will cut down 80% of bounty hunters but the rest will write structured and maintainable code.
What should be done: ~~1. Setup
jest
in the bot's projectpackage.json
~~development
branchdevelopment
branch (as far as I remember we can simply authorize coveralls OAuth app in the bot's repository which brings this functionality out of the box)@ubiquity/software-development Your input is really appreciated.