Decide chocoserver api schema

[taijusanagi]

• use typeORM + nest.js + swagger
• use rest api

[taijusanagi]

v1

This is code first development, so actual development may differ.

only below endpoint is enough for the first development

• contracts
  • input
  • contrat_addresses
  • output
  • name
  • symbol
  • tokens => below
• tokens
  • input
  • owner
  • contract_addresses
  • token_ids
  • order_by
  • order_direction
  • offset
  • limit
  • output
  • array
    • contract_addresses
    • token_id
    • owner
    • metadata
    • image
    • image_data
    • external_url
    • description
    • name
    • attributes
    • background_color
    • animation_url

[taijusanagi]

Chocoserver data

All structure is described here https://github.com/chocomintapp/chocoserver/issues/1#issuecomment-821920631

Chocoserver manage blockchain event and metadata

[taijusanagi]

I need to organize this

network -> block -> transactions -> logs network -> contract

contract and logs are one to many

actually, required query is just contract, then contract returns all log, and log is just analyzed, that's enough

[taijusanagi]

rename log to event, so that not confusing with logging

[taijusanagi]

Basically using graphQL and have REST wrapper is better

Guide for graphQL

• https://blog.logrocket.com/how-to-build-a-graphql-api-with-nestjs/
• https://qiita.com/G-awa/items/3e15f954c42c86aec659

[taijusanagi]

No repository for "Block" was found. Looks like this entity is not registered in current "default" connection? +33ms

nest start and ts-node difference https://stackoverflow.com/questions/45989574/repositorynotfounderror-typeorm/49113172

loading entity for ts-node and nest start is bit different so need to organize it again.

[taijusanagi]

This tutorial says maybe only env value is ok for the migration generation https://blog.theodo.com/2019/05/an-overview-of-nestjs-typeorm-release-your-first-application-in-less-than-30-minutes/

this issue is saying only env is fine https://github.com/typeorm/typeorm/issues/490

But I'm using nestjs/config module pattern, so need to find other way

[taijusanagi]

generating ormconfg.json using env config generate migration and actual migration is done by ormconfig.json nest start is using env config and ts ts-node start

[taijusanagi]

https://docs.nestjs.com/techniques/database

Alternatively, rather than passing a configuration object to forRoot(), we can create an ormconfig.json file in the project root directory.

Ormconfig is only required for the forRoot

[taijusanagi]

I have this provider pattern, but it may not required, just have 1 config is better to manage https://github.com/chocomintapp/chocoserver/blob/a8a781c835baaa0c62b41790a1a9c2ce00730035/src/providers/database/postgres/provider.module.ts

[taijusanagi]

It is better to copy the snapshot in issue to keep tracking

[taijusanagi]

I follow this and config to singleton, without nestjs https://medium.com/@gausmann.simon/nestjs-typeorm-and-postgresql-full-example-development-and-project-setup-working-with-database-c1a2b1b11b8f

[taijusanagi]

How to access relationship ID from Parent's joined field in NestJS/TypeORM https://stackoverflow.com/questions/54163467/how-to-access-relationship-id-from-parents-joined-field-in-nestjs-typeorm

[taijusanagi]

use gRPC for microservice connection and graphql for frontend