WIP: Split up moon counter from the database #489

Draft
Vylpes wants to merge 16 commits from feature/300-moon-set into develop
Owner

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

  • Create a separate moon counter to track how many moons a user has
  • This is so we can start a user at a specific counter
  • Added to the list command a counter to specify how many moons aren't being tracked with the bot

#300

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify the changes. Provide instructions so we can reproduce. Please also list any relevant details to your test configuration.

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that provide my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
# Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. - Create a separate moon counter to track how many moons a user has - This is so we can start a user at a specific counter - Added to the list command a counter to specify how many moons aren't being tracked with the bot #300 ## Type of change Please delete options that are not relevant. - [x] New feature (non-breaking change which adds functionality) # How Has This Been Tested? Please describe the tests that you ran to verify the changes. Provide instructions so we can reproduce. Please also list any relevant details to your test configuration. # Checklist - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that provide my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules
Vylpes added 9 commits 2024-10-29 10:52:14 +00:00
Vylpes requested review from VylpesTester 2024-10-29 10:52:19 +00:00
Vylpes added the
type
story
label 2024-10-29 10:52:26 +00:00
VylpesTester was assigned by Vylpes 2024-10-29 10:52:35 +00:00
Vylpes changed title from Split up moon counter from the database to WIP: Split up moon counter from the database 2024-10-29 10:53:22 +00:00
Vylpes added 1 commit 2024-10-30 09:35:40 +00:00
WIP: Planning list.test.ts
All checks were successful
Test / build (push) Successful in 9s
974e298214
Vylpes added 1 commit 2024-10-31 16:56:39 +00:00
WIP: Planning more tests
All checks were successful
Test / build (push) Successful in 10s
43751e5b02
Vylpes added 3 commits 2024-11-01 17:06:04 +00:00
Vylpes added 1 commit 2024-11-04 18:06:56 +00:00
WIP: Start creating buttonEvent moons list tests
All checks were successful
Test / build (push) Successful in 11s
554c274a7f
Vylpes added 1 commit 2024-11-07 19:38:20 +00:00
WIP: Create add moon command tests
All checks were successful
Test / build (push) Successful in 18s
056783bc44
All checks were successful
Test / build (push) Successful in 18s
Required
Details
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/300-moon-set:feature/300-moon-set
git checkout feature/300-moon-set
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: RabbitLabs/vylbot-app#489
No description provided.