Skip to content

Code Practices #12

Open
Open

Description

@optimm
  • Create a folder repository and all executions with database to be done in repository files (for ex: create auth.repo.ts and create find user, create user functions in there and use in the auth service file) , we can also create a base repository file in future then adding basic functions there.
  • Always create DTOs (classes or interfaces ) for function payload (and for controller functions , validation will also be done by them).
  • Do not use env files directly (just not convenient to use caps), create a file envconfig.ts ,pull all the variables there and use it from there.
  • Naming : Try to name in a way that it is both descriptive and not to long (ex: Function getMe can be renamed to getCurrentUserData.

Activity

  1. github-actions commented on May 29, 2023

    @github-actions

    Welcome to bsoc-bitbyte/busify! 😄 Thank you for reporting your first issue. We truly appreciate your contribution. 🙌

    Please check out our contributors guide to get started. It provides detailed instructions on how to contribute to the Busify project.

    In addition, we recommend going through the guide for a basic setup that will be useful when opening a pull request. This setup will ensure a smooth contribution process.

    If you have any questions or need further assistance, feel free to ask in this issue. Our community is here to help you succeed! 💪

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions