Adding stripe integration by making the server logic independent of the input fields: - query factories (remote server, foreign data wrapper, foreign table) to loop on fields and values without hardcoding the names of the fields - adding stripe input and type - add the logic to handle static schema. Simply creating a big object to store into the server Additional work: - rename username field to user. This is the input intended for postgres user mapping and we now need a matching by name --------- Co-authored-by: Thomas Trompette <thomast@twenty.com>
26 lines
1.2 KiB
TypeScript
26 lines
1.2 KiB
TypeScript
import { Module } from '@nestjs/common';
|
|
import { TypeOrmModule } from '@nestjs/typeorm';
|
|
|
|
import { ForeignDataWrapperServerQueryFactory } from 'src/engine/api/graphql/workspace-query-builder/factories/foreign-data-wrapper-server-query.factory';
|
|
import { FeatureFlagEntity } from 'src/engine/core-modules/feature-flag/feature-flag.entity';
|
|
import { RemoteServerEntity } from 'src/engine/metadata-modules/remote-server/remote-server.entity';
|
|
import { RemoteServerResolver } from 'src/engine/metadata-modules/remote-server/remote-server.resolver';
|
|
import { RemoteServerService } from 'src/engine/metadata-modules/remote-server/remote-server.service';
|
|
import { RemoteTableModule } from 'src/engine/metadata-modules/remote-server/remote-table/remote-table.module';
|
|
import { WorkspaceDataSourceModule } from 'src/engine/workspace-datasource/workspace-datasource.module';
|
|
|
|
@Module({
|
|
imports: [
|
|
TypeOrmModule.forFeature([RemoteServerEntity], 'metadata'),
|
|
RemoteTableModule,
|
|
WorkspaceDataSourceModule,
|
|
TypeOrmModule.forFeature([FeatureFlagEntity], 'core'),
|
|
],
|
|
providers: [
|
|
RemoteServerService,
|
|
RemoteServerResolver,
|
|
ForeignDataWrapperServerQueryFactory,
|
|
],
|
|
})
|
|
export class RemoteServerModule {}
|