Skip to content
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

next v2.6.0 #440

Merged
merged 14 commits into from
Jul 30, 2024
Merged

next v2.6.0 #440

merged 14 commits into from
Jul 30, 2024

Conversation

MartinBenediktBusch
Copy link
Collaborator

@MartinBenediktBusch MartinBenediktBusch commented Jul 3, 2024

next v2.6.0 version

* add vote model to forum questions

* add voting models

* add COCM model as default
@MartinBenediktBusch MartinBenediktBusch added the DO NOT MERGE Do not merge this pull request label Jul 3, 2024
@MartinBenediktBusch MartinBenediktBusch marked this pull request as draft July 3, 2024 15:47
@MartinBenediktBusch MartinBenediktBusch changed the title nextv2.6.0 next v2.6.0 Jul 3, 2024
diegoalzate and others added 9 commits July 3, 2024 20:50
* rename db tables to have more consistency

* fix renaming variables

* fix tests

* update property names

* drop db changes

* create new migration starting from vote model changes

* update github actions pnpm setup to v4 to stop breaking actions issue

* fix tests

---------

Co-authored-by: Martin Benedikt Busch <[email protected]>
* initial event registration changes

* get validation working on event registrations

* fix handler validation

* add new fields to options and questions

* add linking group to option

* fix tests

* minor naming fixes

* rename validateEventRegistrationFields to validateEventFields, to keep consistency with options

* seed event fields

* add fields to seed function

* make sure fields seed with uuid

* check if event exists

---------

Co-authored-by: Martin Benedikt Busch <[email protected]>
* make group category id required

* add ts-docstring

* avoid quering question id at each plural score calculation

* separate vote validation from saving

* separate validation and saving from updating the vote score

* update tests

* implemented suggestions

* refactor updateOptionScore function

* drop migration

* add db migration

* update tests and remove dependencies
* initial event registration changes

* get validation working on event registrations

* fix handler validation

* add new fields to options and questions

* add linking group to option

* fix tests

* create api endpoints for users to create options

* add userCanCreate to questions table

* add api endpoints for options

* fix tests

* fix migrations

* fix drizzle journal

* remove unused dependency

* fix wrong registration name in wrong service
* add tests for the user service

* fix linting

* test funding mechanism and refactor service

* resolve lint warnings
* add pino

* replace console with logger

* fix conflicts

* update errors

* remove unused import
* organize db functions inside db folder

* wip: migrate seed data

* fix tests imports

* update logger for testing

* add node test runner

* make all tests pass

* allow parallel testing

* update logger types

* update ci test

* fix build issues

* add test coverage

* remove nyc output

* remove index from nyc output

* fix seed script

* exclude spec files from report

---------

Co-authored-by: Martin Benedikt Busch <[email protected]>
Copy link

coderabbitai bot commented Jul 19, 2024

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

52 files out of 124 files are above the max files limit of 50. Please upgrade to Pro plan to get higher limits.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

diegoalzate and others added 2 commits July 25, 2024 10:52
* update validation schema

* update fields object to be dict and not array

* fix tests
* add registration to seed

* Update src/db/seed.ts

Co-authored-by: Martin Benedikt Busch <[email protected]>

---------

Co-authored-by: Martin Benedikt Busch <[email protected]>
@diegoalzate diegoalzate marked this pull request as ready for review July 26, 2024 09:28
* add status to events

* evaluate upcoming before closed
@diegoalzate diegoalzate removed the DO NOT MERGE Do not merge this pull request label Jul 30, 2024
@diegoalzate diegoalzate merged commit 96d3e37 into develop Jul 30, 2024
3 checks passed
@diegoalzate diegoalzate deleted the next-v2.6.0 branch July 30, 2024 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants