deep-foundation / boilerplate Goto Github PK

• packages directory with npm publish script
• typescript with linting
• env base config
• tests

• independend npm packages
• packages in submodules monorepo
• fully ts
• mobile app as one nextjs page route with query args
• better graph editor with cards admin system
• gql query generator in any places, with save queries in url
• auto drawing maps of node types
• independend migrations of system, damp of models and settings, damp of data

what else?

https://github.com/deepcase/boilerplate/blob/bd85d64119dc5ef99b71a78f7ebe840fdc2b7a89/packages/migrations/migrations/1603872676665-pgsql-nodes-init.ts#L13-L16

Probably there are similar problems in other migrations.

• life range prognosis
• Work/free/sleep/eat/talk/road ranges
• calendar years/mouths/weeks/days/hours of life with filter by ranges

• Initiate miband sync for fill prognosis
• Initiate issues for detect other life processes
• Initiate issues for resource analysis, wallet model, add number model, transaction model
  • Initiate issues for prognosis wallets dynamicy

https://github.com/deepcase/boilerplate/blob/bd85d64119dc5ef99b71a78f7ebe840fdc2b7a89/packages/migrations/migrations/1603872676665-pgsql-nodes-init.ts#L19

Probably there are similar problems in other migrations.

I had this error.

ERROR: Your dev environment is running Node.js version v13.11.0 which does not meet the
requirements for building this repository.  (The rush.json configuration requires
nodeSupportedVersionRange=">=12.13.0 <13.0.0")

• nodes sql-js trigger
• hasura event-handler
• realization of push sender

we have realizaed prototype from previous projects, need to refactor and reanalize

- [ ] jws/token auth
- [ ] move from private deepcase repo realized auth with secred code (sms/email... any)
- [ ] move from private deepcase repo realized password auth

• check compatibility with passportjs package with many auth methods

auto stop and start subscriptions when visibility sensor on/off

https://github.com/deepcase/boilerplate/blob/4d8d2e2db9cbe69a6cb8e9b173cf0f12bbc40240/packages/migrations/imports/hasura.ts#L10-L22

https://github.com/deepcase/boilerplate/blob/4d8d2e2db9cbe69a6cb8e9b173cf0f12bbc40240/packages/migrations/imports/hasura.ts#L23-L30

Properties method, url, headers are identical in both these methods. Therefore we can use DRY here.

available only after teamleads approve concept

• d3 force graph with jumps to nodes and links
• node card with auto generated based on node-links context model understanding
• insert nodes, links, hole models
• model constructor, where as part can be used nodes, links and other models
• visual hightlightning selectors by visible part of graph

• integrated transactioned migrations for postgres and hasura metadata
• easy local starter
• apollo/relay connector
• event-handler boilerplate in nextjs api
• remote-schema boilerplate in nextjs api

• tested basic tree and multiparental tree combinations
• test with random tree
• test with random multiparental tree

My old reson to include compiled code in sources - easy to import from git. But if i want to import git, i can use after install script in npm and call building there.

for now we support only http header tokens for hasura auth

need to research and develop jws tokens realization

for now, auth package is working only with cookies store and http requests, need to add ajax requests to auth servers and capacitor storage