kudoo-cloud/kudoo

The Kudoo business application. Includes both the front end and back end

kudoo's Issues

Add LGTM for continuous security analysis

**Is your feature request related to a problem? Please describe.
We don't have the ability to automatically report on security issues in Pull Requests

Describe the solution you'd like
I'd like to use LGTM similar to the way the Gitea projects uses it

Describe alternatives you've considered
We could also use SonarQube, but that will require pricing and isn't as specialised.

Replace S3 Storage with Arweave

We will encrypt all files and store them on Arweave rather than rely on centralized cloud storage providers

Manufacturing

I'll keep updating this issue periodically. This issue will be used to specify the design of the manufacturing functionality and specifically the following items:

• Items
• Bill of materials
• Formulas
• Routes and operations
• Production orders
• Master planning
• Master scheduling

Installation - run.sh not working

Script directory references don't match repo dirs in /kudoo.

btw: Was able to get everything going by starting things manually in the frontend / backend directories. Just wondering how to login? I get: Error: Network error: Failed to fetch when creating an account. Also get that at the live site too: kudoo.io. I jumped into Postgres and noticed a kudoo_dev database was created but no tables present. Do I need to run anything else from the other directories? (i.e. /graphql)

On the upside - this project looks really nice. I'd like to look at it more.

Add logging in with Metamask

https://docs.avax.network/build/tutorials/smart-contracts/add-avalanche-to-metamask-programmatically

Kudoo uses Redux pretty heavily (currently on 3, so might be good to upgrade to 4 at the same time)

So for us to log in with Metamask, we'll then need to make sure that isLoggedIn is set to true

So this issue will need to do the following:

• Add Connect Wallet to the Login component https://docs.metamask.io/guide/getting-started.html#basic-considerations
• Once a user has Connected their wallet, then we should change the Redux state Profile -> isLoggedIn to true

We'll also need to add another bit of Redux state. Under profile, we should add an Avalanche section with the following fields:

• Blockchain - Enum with value ['Avalanche'] We'll may go cross chain one day
• C-Chain Address
• X-Chain Address

Create Text Invoice Step 4 - Invoice number is incorrect

Describe the bug
If you look at the below screenshot you can see that the Invoice number has been randomly generated

This screen is meant as a Review screen before the Invoice is created. Therefore the GraphQL Server hasn't generated the Invoice number at this point.

This means under src/screens/common/invoices/CreateInvoice/ReviewStep.tsx on line 75

this.invoiceNumber = Math.floor(Math.random() * 90000) + 10000;

We can replace this with a string stating Will be generated after saving.

However we also generate a PDF through jsPDF as seen on Line 803.

This will mean then that we'll have to change this so that we only generate the PDF after the Invoice has been created

Upgrade to React 17

Self explanatory

Remove Prisma and add new GraphQL functionality

Currently we are using Prisma v1. I'm not the biggest fan of the Prisma project and it adds a lot of overhead in terms of the Docker image.

We'll rewrite the backend in Nestjs.

First entities to build are (schema can be found here https://github.com/kudoo-cloud/kudoo/blob/master/server/prisma/ERP.graphql):

• User - Need to add the following extra fields [Blockchain, X-Chain Address, C-Chain Address, Telegram handle, Discord handle]
• Company - Needs to be renamed to DAO. Also needs extra fields [Token address, Blockchain]
• CompanyMember - Needs to be renamed to DAOMember
• Supplier - Remove bankaccount and replace it with [Blockchain, C-Chain address, X-chain address]
• Service - Add a relationship to Supplier

Move Configuration into TOML format

Currently we have a bunch of configuration strewn throughout the app. All this configuration is written in JSON and Typescript in multiple locations.

I’d like to move to common configuration file that controls the entire app. I’ve researched many formats and it appears as if TOML will be the best for our use case. One of the reasons for TOML is that it’s friendly for both machines and humans. YAML was also under consideration but it’s too vague in it’s meanings in a lot of instances which will cause undue confusion.

So I’d propose we move forward with the following:

[apps]
    [apps.projects]
    enabled = true
    name = "Projects"
        [apps.projects.menus]
            [apps.projects.menus.dashboard]
            name = "Dashboard"
            # We can leave our order as we'll infer it from the TOML order,
            availability.securityrole = "ADMIN"
            availability.country = "AU"
            availability.businessType = "HEALTH"
            icon = "icon icon-dashboard"
            url = "DASHBOARD"
            # isActive doesn't need to appear in the TOML
    [apps.finance]
    enabled = false
    [apps.inventory]
    enabled = false
    [apps.health]
    enabled = false
    [apps.manufacturing]
    enabled = false

Upgrade to Apollo Client 3

This will also entail removing all HOC's and will deprecate the Kudoo GraphQL library.