Amin'izao fotoana izao, ny REST API dia lasa fenitra ho an'ny fampivoarana ny rindranasa amin'ny tranonkala, mamela ny fampandrosoana hozaraina ho ampahany tsy miankina. Ny rafitra malaza isan-karazany toy ny Angular, React, Vue ary ny hafa dia ampiasaina amin'izao fotoana izao ho an'ny UI. Ny mpandrindra backend dia afaka misafidy amin'ny fiteny sy rafitra isan-karazany. Androany aho dia te hiresaka momba ny rafitra toy izany NestJS. Inty izahay TestMace Ampiasainay am-pahavitrihana amin'ny tetikasa anatiny izany. Mampiasa akany sy fonosana @nestjsx/crud, hamorona fampiharana CRUD tsotra izahay.

Nahoana i NestJS

Vao haingana, be dia be ny rafitra backend niseho tao amin'ny vondrom-piarahamonina JavaScript. Ary raha amin'ny lafiny fiasa dia manome fahaiza-manao mitovy amin'ny Nest izy ireo, dia amin'ny zavatra iray dia azo antoka fa mandresy - izany no maritrano. Ireto endri-javatra NestJS manaraka ireto dia ahafahanao mamorona rindranasa indostrialy sy mivelatra amin'ny ekipa lehibe:

• mampiasa TypeScript ho fiteny fampandrosoana lehibe. Na dia manohana JavaScript aza ny NestJS, dia mety tsy mandeha ny fiasa sasany, indrindra raha miresaka momba ny fonosana antoko fahatelo isika;
• ny fisian'ny kaontenera DI, izay ahafahanao mamorona singa mifamatotra;
• Ny fiasan'ny rafitra mihitsy dia mizara ho singa tsy miankina azo ovaina. Ohatra, eo ambanin'ny satroka ho toy ny rafitra azo ampiasaina ho toy ny maneho, ary mifady hanina, mba hiasa amin'ny angon-drakitra, ny akany ivelan'ny boaty dia manome fatorana amin'ny typeorm, mongoose, sequelize;
• NestJS dia sehatra agnostika ary manohana ny REST, GraphQL, Websockets, gRPC, sns.

Ny framework mihitsy dia aingam-panahy avy amin'ny framework frontend Angular ary misy fitoviana be amin'izany.

Fametrahana ny NestJS sy fametrahana ny tetikasa

Misy fonosana ny Nest akaniny/cli, izay ahafahanao mametraka haingana rafitra fampiharana fototra. Andao hametraka ity fonosana ity maneran-tany:

npm install --global @nest/cli

Aorian'ny fametrahana dia hamorona ny rafitra fototra amin'ny fampiharana misy ny anarana izahay nest-rest. Izany dia atao amin'ny fampiasana ny baiko nest new nest-rest.

akany vaovao fitsaharana

dmitrii@dmitrii-HP-ZBook-17-G3:~/projects $ nest new nest-rest
  We will scaffold your app in a few seconds..

CREATE /nest-rest/.prettierrc (51 bytes)
CREATE /nest-rest/README.md (3370 bytes)
CREATE /nest-rest/nest-cli.json (84 bytes)
CREATE /nest-rest/nodemon-debug.json (163 bytes)
CREATE /nest-rest/nodemon.json (67 bytes)
CREATE /nest-rest/package.json (1805 bytes)
CREATE /nest-rest/tsconfig.build.json (97 bytes)
CREATE /nest-rest/tsconfig.json (325 bytes)
CREATE /nest-rest/tslint.json (426 bytes)
CREATE /nest-rest/src/app.controller.spec.ts (617 bytes)
CREATE /nest-rest/src/app.controller.ts (274 bytes)
CREATE /nest-rest/src/app.module.ts (249 bytes)
CREATE /nest-rest/src/app.service.ts (142 bytes)
CREATE /nest-rest/src/main.ts (208 bytes)
CREATE /nest-rest/test/app.e2e-spec.ts (561 bytes)
CREATE /nest-rest/test/jest-e2e.json (183 bytes)

? Which package manager would you ️ to use? yarn
 Installation in progress... 

  Successfully created project nest-rest
  Get started with the following commands:

$ cd nest-rest
$ yarn run start

                          Thanks for installing Nest 
                 Please consider donating to our open collective
                        to help us maintain this package.

                 Donate: https://opencollective.com/nest

Hifidy kofehy izahay ho mpitantana ny fonosana.
Amin'izao fotoana izao dia afaka manomboka ny mpizara amin'ny baiko ianao npm start ary mandeha any amin'ny adiresy http://localhost:3000 azonao jerena ny pejy fototra. Na izany aza, tsy izany no antony nivondronantsika teto ary mandroso isika.

Fametrahana asa miaraka amin'ny angon-drakitra

Nifidy PostrgreSQL ho DBMS ho an'ity lahatsoratra ity aho. Tsy misy fifandirana momba ny tsiro, raha ny hevitro dia ity no DBMS matotra indrindra, manana ny fahaiza-manao ilaina rehetra. Araka ny efa voalaza, ny Nest dia manome fampidirana miaraka amin'ny fonosana isan-karazany mba hiasa amin'ny angon-drakitra. SATRIA Satria nianjera tamin'ny PostgreSQL ny safidiko, dia mety ho lojika ny misafidy TypeORM ho ORM. Andao hametraka ny fonosana ilaina amin'ny fampidirana amin'ny angon-drakitra:

yarn add typeorm @nestjs/typeorm pg

Amin'ny filaharana, inona no ilaina isaky ny fonosana:

1. typeorm - fonosana mivantana avy amin'ny ORM mihitsy;
2. @nestjs/typeorm - fonosana TypeORM ho an'ny NestJS. Manampy modules ho an'ny fanafarana ao amin'ny maody tetikasa, ary koa andiana mpanaingo mpanampy;
3. pg - mpamily miasa amin'ny PostgreSQL.

Okay, napetraka ny fonosana, mila manomboka ny angon-drakitra ianao izao. Mba hametrahana ny angon-drakitra dia hampiasa docker-compose.yml miaraka amin'ity atiny manaraka ity aho:

docker-compose.yml

version: '3.1'

services:
  db:
    image: postgres:11.2
    restart: always
    environment:
      POSTGRES_PASSWORD: example
    volumes:
      - ../db:/var/lib/postgresql/data
      - ./postgresql.conf:/etc/postgresql/postgresql.conf
    ports:
      - 5432:5432
  adminer:
    image: adminer
    restart: always
    ports:
      - 8080:8080

Araka ny hitanao, ity rakitra ity dia manamboatra ny fandefasana container 2:

1. db dia container misy mivantana ny angon-drakitra. Amin'ny tranga misy antsika, postgresql version 11.2 no ampiasaina;
2. adminer — mpitantana ny angona. Manome interface tsara amin'ny tranonkala hijerena sy hitantanana ny angon-drakitra.

Mba hiasa amin'ny fifandraisana tcp dia nampiako ity config.

postgresql.conf

# -----------------------------
# PostgreSQL configuration file
# -----------------------------
#
# This file consists of lines of the form:
#
#   name = value
#
# (The "=" is optional.)  Whitespace may be used.  Comments are introduced with
# "#" anywhere on a line.  The complete list of parameter names and allowed
# values can be found in the PostgreSQL documentation.
#
# The commented-out settings shown in this file represent the default values.
# Re-commenting a setting is NOT sufficient to revert it to the default value;
# you need to reload the server.
#
# This file is read on server startup and when the server receives a SIGHUP
# signal.  If you edit the file on a running system, you have to SIGHUP the
# server for the changes to take effect, run "pg_ctl reload", or execute
# "SELECT pg_reload_conf()".  Some parameters, which are marked below,
# require a server shutdown and restart to take effect.
#
# Any parameter can also be given as a command-line option to the server, e.g.,
# "postgres -c log_connections=on".  Some parameters can be changed at run time
# with the "SET" SQL command.
#
# Memory units:  kB = kilobytes        Time units:  ms  = milliseconds
#                MB = megabytes                     s   = seconds
#                GB = gigabytes                     min = minutes
#                TB = terabytes                     h   = hours
#                                                   d   = days
#------------------------------------------------------------------------------
# FILE LOCATIONS
#------------------------------------------------------------------------------
# The default values of these variables are driven from the -D command-line
# option or PGDATA environment variable, represented here as ConfigDir.
#data_directory = 'ConfigDir'       # use data in another directory
# (change requires restart)
#hba_file = 'ConfigDir/pg_hba.conf' # host-based authentication file
# (change requires restart)
#ident_file = 'ConfigDir/pg_ident.conf' # ident configuration file
# (change requires restart)
# If external_pid_file is not explicitly set, no extra PID file is written.
#external_pid_file = ''         # write an extra PID file
# (change requires restart)
#------------------------------------------------------------------------------
# CONNECTIONS AND AUTHENTICATION
#------------------------------------------------------------------------------
# - Connection Settings -
listen_addresses = '*'
#listen_addresses = 'localhost'     # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost'; use '*' for all
# (change requires restart)
#port = 5432                # (change requires restart)
#max_connections = 100          # (change requires restart)
#superuser_reserved_connections = 3 # (change requires restart)
#unix_socket_directories = '/tmp'   # comma-separated list of directories
# (change requires restart)
#unix_socket_group = ''         # (change requires restart)
#unix_socket_permissions = 0777     # begin with 0 to use octal notation
# (change requires restart)
#bonjour = off              # advertise server via Bonjour
# (change requires restart)
#bonjour_name = ''          # defaults to the computer name
# (change requires restart)
# - TCP Keepalives -
# see "man 7 tcp" for details
#tcp_keepalives_idle = 0        # TCP_KEEPIDLE, in seconds;
# 0 selects the system default
#tcp_keepalives_interval = 0        # TCP_KEEPINTVL, in seconds;
# 0 selects the system default
#tcp_keepalives_count = 0       # TCP_KEEPCNT;
# 0 selects the system default
# - Authentication -
#authentication_timeout = 1min      # 1s-600s
#password_encryption = md5      # md5 or scram-sha-256
#db_user_namespace = off
# GSSAPI using Kerberos
#krb_server_keyfile = ''
#krb_caseins_users = off
# - SSL -
#ssl = off
#ssl_ca_file = ''
#ssl_cert_file = 'server.crt'
#ssl_crl_file = ''
#ssl_key_file = 'server.key'
#ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL' # allowed SSL ciphers
#ssl_prefer_server_ciphers = on
#ssl_ecdh_curve = 'prime256v1'
#ssl_min_protocol_version = 'TLSv1'
#ssl_max_protocol_version = ''
#ssl_dh_params_file = ''
#ssl_passphrase_command = ''
#ssl_passphrase_command_supports_reload = off
#------------------------------------------------------------------------------
# RESOURCE USAGE (except WAL)
#------------------------------------------------------------------------------
# - Memory -
#shared_buffers = 32MB          # min 128kB
# (change requires restart)
#huge_pages = try           # on, off, or try
# (change requires restart)
#temp_buffers = 8MB         # min 800kB
#max_prepared_transactions = 0      # zero disables the feature
# (change requires restart)
# Caution: it is not advisable to set max_prepared_transactions nonzero unless
# you actively intend to use prepared transactions.
#work_mem = 4MB             # min 64kB
#maintenance_work_mem = 64MB        # min 1MB
#autovacuum_work_mem = -1       # min 1MB, or -1 to use maintenance_work_mem
#max_stack_depth = 2MB          # min 100kB
#shared_memory_type = mmap      # the default is the first option
# supported by the operating system:
#   mmap
#   sysv
#   windows
# (change requires restart)
#dynamic_shared_memory_type = posix # the default is the first option
# supported by the operating system:
#   posix
#   sysv
#   windows
#   mmap
# (change requires restart)
# - Disk -
#temp_file_limit = -1           # limits per-process temp file space
# in kB, or -1 for no limit
# - Kernel Resources -
#max_files_per_process = 1000       # min 25
# (change requires restart)
# - Cost-Based Vacuum Delay -
#vacuum_cost_delay = 0          # 0-100 milliseconds (0 disables)
#vacuum_cost_page_hit = 1       # 0-10000 credits
#vacuum_cost_page_miss = 10     # 0-10000 credits
#vacuum_cost_page_dirty = 20        # 0-10000 credits
#vacuum_cost_limit = 200        # 1-10000 credits
# - Background Writer -
#bgwriter_delay = 200ms         # 10-10000ms between rounds
#bgwriter_lru_maxpages = 100        # max buffers written/round, 0 disables
#bgwriter_lru_multiplier = 2.0      # 0-10.0 multiplier on buffers scanned/round
#bgwriter_flush_after = 0       # measured in pages, 0 disables
# - Asynchronous Behavior -
#effective_io_concurrency = 1       # 1-1000; 0 disables prefetching
#max_worker_processes = 8       # (change requires restart)
#max_parallel_maintenance_workers = 2   # taken from max_parallel_workers
#max_parallel_workers_per_gather = 2    # taken from max_parallel_workers
#parallel_leader_participation = on
#max_parallel_workers = 8       # maximum number of max_worker_processes that
# can be used in parallel operations
#old_snapshot_threshold = -1        # 1min-60d; -1 disables; 0 is immediate
# (change requires restart)
#backend_flush_after = 0        # measured in pages, 0 disables
#------------------------------------------------------------------------------
# WRITE-AHEAD LOG
#------------------------------------------------------------------------------
# - Settings -
#wal_level = replica            # minimal, replica, or logical
# (change requires restart)
#fsync = on             # flush data to disk for crash safety
# (turning this off can cause
# unrecoverable data corruption)
#synchronous_commit = on        # synchronization level;
# off, local, remote_write, remote_apply, or on
#wal_sync_method = fsync        # the default is the first option
# supported by the operating system:
#   open_datasync
#   fdatasync (default on Linux)
#   fsync
#   fsync_writethrough
#   open_sync
#full_page_writes = on          # recover from partial page writes
#wal_compression = off          # enable compression of full-page writes
#wal_log_hints = off            # also do full page writes of non-critical updates
# (change requires restart)
#wal_buffers = -1           # min 32kB, -1 sets based on shared_buffers
# (change requires restart)
#wal_writer_delay = 200ms       # 1-10000 milliseconds
#wal_writer_flush_after = 1MB       # measured in pages, 0 disables
#commit_delay = 0           # range 0-100000, in microseconds
#commit_siblings = 5            # range 1-1000
# - Checkpoints -
#checkpoint_timeout = 5min      # range 30s-1d
#max_wal_size = 1GB
#min_wal_size = 80MB
#checkpoint_completion_target = 0.5 # checkpoint target duration, 0.0 - 1.0
#checkpoint_flush_after = 0     # measured in pages, 0 disables
#checkpoint_warning = 30s       # 0 disables
# - Archiving -
#archive_mode = off     # enables archiving; off, on, or always
# (change requires restart)
#archive_command = ''       # command to use to archive a logfile segment
# placeholders: %p = path of file to archive
#               %f = file name only
# e.g. 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f'
#archive_timeout = 0        # force a logfile segment switch after this
# number of seconds; 0 disables
# - Archive Recovery -
# These are only used in recovery mode.
#restore_command = ''       # command to use to restore an archived logfile segment
# placeholders: %p = path of file to restore
#               %f = file name only
# e.g. 'cp /mnt/server/archivedir/%f %p'
# (change requires restart)
#archive_cleanup_command = ''   # command to execute at every restartpoint
#recovery_end_command = ''  # command to execute at completion of recovery
# - Recovery Target -
# Set these only when performing a targeted recovery.
#recovery_target = ''       # 'immediate' to end recovery as soon as a
# consistent state is reached
# (change requires restart)
#recovery_target_name = ''  # the named restore point to which recovery will proceed
# (change requires restart)
#recovery_target_time = ''  # the time stamp up to which recovery will proceed
# (change requires restart)
#recovery_target_xid = ''   # the transaction ID up to which recovery will proceed
# (change requires restart)
#recovery_target_lsn = ''   # the WAL LSN up to which recovery will proceed
# (change requires restart)
#recovery_target_inclusive = on # Specifies whether to stop:
# just after the specified recovery target (on)
# just before the recovery target (off)
# (change requires restart)
#recovery_target_timeline = 'latest'    # 'current', 'latest', or timeline ID
# (change requires restart)
#recovery_target_action = 'pause'   # 'pause', 'promote', 'shutdown'
# (change requires restart)
#------------------------------------------------------------------------------
# REPLICATION
#------------------------------------------------------------------------------
# - Sending Servers -
# Set these on the master and on any standby that will send replication data.
#max_wal_senders = 10       # max number of walsender processes
# (change requires restart)
#wal_keep_segments = 0      # in logfile segments; 0 disables
#wal_sender_timeout = 60s   # in milliseconds; 0 disables
#max_replication_slots = 10 # max number of replication slots
# (change requires restart)
#track_commit_timestamp = off   # collect timestamp of transaction commit
# (change requires restart)
# - Master Server -
# These settings are ignored on a standby server.
#synchronous_standby_names = '' # standby servers that provide sync rep
# method to choose sync standbys, number of sync standbys,
# and comma-separated list of application_name
# from standby(s); '*' = all
#vacuum_defer_cleanup_age = 0   # number of xacts by which cleanup is delayed
# - Standby Servers -
# These settings are ignored on a master server.
#primary_conninfo = ''          # connection string to sending server
# (change requires restart)
#primary_slot_name = ''         # replication slot on sending server
# (change requires restart)
#promote_trigger_file = ''      # file name whose presence ends recovery
#hot_standby = on           # "off" disallows queries during recovery
# (change requires restart)
#max_standby_archive_delay = 30s    # max delay before canceling queries
# when reading WAL from archive;
# -1 allows indefinite delay
#max_standby_streaming_delay = 30s  # max delay before canceling queries
# when reading streaming WAL;
# -1 allows indefinite delay
#wal_receiver_status_interval = 10s # send replies at least this often
# 0 disables
#hot_standby_feedback = off     # send info from standby to prevent
# query conflicts
#wal_receiver_timeout = 60s     # time that receiver waits for
# communication from master
# in milliseconds; 0 disables
#wal_retrieve_retry_interval = 5s   # time to wait before retrying to
# retrieve WAL after a failed attempt
#recovery_min_apply_delay = 0       # minimum delay for applying changes during recovery
# - Subscribers -
# These settings are ignored on a publisher.
#max_logical_replication_workers = 4    # taken from max_worker_processes
# (change requires restart)
#max_sync_workers_per_subscription = 2  # taken from max_logical_replication_workers
#------------------------------------------------------------------------------
# QUERY TUNING
#------------------------------------------------------------------------------
# - Planner Method Configuration -
#enable_bitmapscan = on
#enable_hashagg = on
#enable_hashjoin = on
#enable_indexscan = on
#enable_indexonlyscan = on
#enable_material = on
#enable_mergejoin = on
#enable_nestloop = on
#enable_parallel_append = on
#enable_seqscan = on
#enable_sort = on
#enable_tidscan = on
#enable_partitionwise_join = off
#enable_partitionwise_aggregate = off
#enable_parallel_hash = on
#enable_partition_pruning = on
# - Planner Cost Constants -
#seq_page_cost = 1.0            # measured on an arbitrary scale
#random_page_cost = 4.0         # same scale as above
#cpu_tuple_cost = 0.01          # same scale as above
#cpu_index_tuple_cost = 0.005       # same scale as above
#cpu_operator_cost = 0.0025     # same scale as above
#parallel_tuple_cost = 0.1      # same scale as above
#parallel_setup_cost = 1000.0   # same scale as above
#jit_above_cost = 100000        # perform JIT compilation if available
# and query more expensive than this;
# -1 disables
#jit_inline_above_cost = 500000     # inline small functions if query is
# more expensive than this; -1 disables
#jit_optimize_above_cost = 500000   # use expensive JIT optimizations if
# query is more expensive than this;
# -1 disables
#min_parallel_table_scan_size = 8MB
#min_parallel_index_scan_size = 512kB
#effective_cache_size = 4GB
# - Genetic Query Optimizer -
#geqo = on
#geqo_threshold = 12
#geqo_effort = 5            # range 1-10
#geqo_pool_size = 0         # selects default based on effort
#geqo_generations = 0           # selects default based on effort
#geqo_selection_bias = 2.0      # range 1.5-2.0
#geqo_seed = 0.0            # range 0.0-1.0
# - Other Planner Options -
#default_statistics_target = 100    # range 1-10000
#constraint_exclusion = partition   # on, off, or partition
#cursor_tuple_fraction = 0.1        # range 0.0-1.0
#from_collapse_limit = 8
#join_collapse_limit = 8        # 1 disables collapsing of explicit
# JOIN clauses
#force_parallel_mode = off
#jit = on               # allow JIT compilation
#plan_cache_mode = auto         # auto, force_generic_plan or
# force_custom_plan
#------------------------------------------------------------------------------
# REPORTING AND LOGGING
#------------------------------------------------------------------------------
# - Where to Log -
#log_destination = 'stderr'     # Valid values are combinations of
# stderr, csvlog, syslog, and eventlog,
# depending on platform.  csvlog
# requires logging_collector to be on.
# This is used when logging to stderr:
#logging_collector = off        # Enable capturing of stderr and csvlog
# into log files. Required to be on for
# csvlogs.
# (change requires restart)
# These are only used if logging_collector is on:
#log_directory = 'log'          # directory where log files are written,
# can be absolute or relative to PGDATA
#log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log'    # log file name pattern,
# can include strftime() escapes
#log_file_mode = 0600           # creation mode for log files,
# begin with 0 to use octal notation
#log_truncate_on_rotation = off     # If on, an existing log file with the
# same name as the new log file will be
# truncated rather than appended to.
# But such truncation only occurs on
# time-driven rotation, not on restarts
# or size-driven rotation.  Default is
# off, meaning append to existing files
# in all cases.
#log_rotation_age = 1d          # Automatic rotation of logfiles will
# happen after that time.  0 disables.
#log_rotation_size = 10MB       # Automatic rotation of logfiles will
# happen after that much log output.
# 0 disables.
# These are relevant when logging to syslog:
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'
#syslog_sequence_numbers = on
#syslog_split_messages = on
# This is only relevant when logging to eventlog (win32):
# (change requires restart)
#event_source = 'PostgreSQL'
# - When to Log -
#log_min_messages = warning     # values in order of decreasing detail:
#   debug5
#   debug4
#   debug3
#   debug2
#   debug1
#   info
#   notice
#   warning
#   error
#   log
#   fatal
#   panic
#log_min_error_statement = error    # values in order of decreasing detail:
#   debug5
#   debug4
#   debug3
#   debug2
#   debug1
#   info
#   notice
#   warning
#   error
#   log
#   fatal
#   panic (effectively off)
#log_min_duration_statement = -1    # logs statements and their durations
# according to log_statement_sample_rate. -1 is disabled,
# 0 logs all statement, > 0 logs only statements running at
# least this number of milliseconds.
#log_statement_sample_rate = 1  # Fraction of logged statements over
# log_min_duration_statement. 1.0 logs all statements,
# 0 never logs.
# - What to Log -
#debug_print_parse = off
#debug_print_rewritten = off
#debug_print_plan = off
#debug_pretty_print = on
#log_checkpoints = off
#log_connections = off
#log_disconnections = off
#log_duration = off
#log_error_verbosity = default      # terse, default, or verbose messages
#log_hostname = off
#log_line_prefix = '%m [%p] '       # special values:
#   %a = application name
#   %u = user name
#   %d = database name
#   %r = remote host and port
#   %h = remote host
#   %p = process ID
#   %t = timestamp without milliseconds
#   %m = timestamp with milliseconds
#   %n = timestamp with milliseconds (as a Unix epoch)
#   %i = command tag
#   %e = SQL state
#   %c = session ID
#   %l = session line number
#   %s = session start timestamp
#   %v = virtual transaction ID
#   %x = transaction ID (0 if none)
#   %q = stop here in non-session
#        processes
#   %% = '%'
# e.g. '<%u%%%d> '
#log_lock_waits = off           # log lock waits >= deadlock_timeout
#log_statement = 'none'         # none, ddl, mod, all
#log_replication_commands = off
#log_temp_files = -1            # log temporary files equal or larger
# than the specified size in kilobytes;
# -1 disables, 0 logs all temp files
#log_timezone = 'GMT'
#------------------------------------------------------------------------------
# PROCESS TITLE
#------------------------------------------------------------------------------
#cluster_name = ''          # added to process titles if nonempty
# (change requires restart)
#update_process_title = on
#------------------------------------------------------------------------------
# STATISTICS
#------------------------------------------------------------------------------
# - Query and Index Statistics Collector -
#track_activities = on
#track_counts = on
#track_io_timing = off
#track_functions = none         # none, pl, all
#track_activity_query_size = 1024   # (change requires restart)
#stats_temp_directory = 'pg_stat_tmp'
# - Monitoring -
#log_parser_stats = off
#log_planner_stats = off
#log_executor_stats = off
#log_statement_stats = off
#------------------------------------------------------------------------------
# AUTOVACUUM
#------------------------------------------------------------------------------
#autovacuum = on            # Enable autovacuum subprocess?  'on'
# requires track_counts to also be on.
#log_autovacuum_min_duration = -1   # -1 disables, 0 logs all actions and
# their durations, > 0 logs only
# actions running at least this number
# of milliseconds.
#autovacuum_max_workers = 3     # max number of autovacuum subprocesses
# (change requires restart)
#autovacuum_naptime = 1min      # time between autovacuum runs
#autovacuum_vacuum_threshold = 50   # min number of row updates before
# vacuum
#autovacuum_analyze_threshold = 50  # min number of row updates before
# analyze
#autovacuum_vacuum_scale_factor = 0.2   # fraction of table size before vacuum
#autovacuum_analyze_scale_factor = 0.1  # fraction of table size before analyze
#autovacuum_freeze_max_age = 200000000  # maximum XID age before forced vacuum
# (change requires restart)
#autovacuum_multixact_freeze_max_age = 400000000    # maximum multixact age
# before forced vacuum
# (change requires restart)
#autovacuum_vacuum_cost_delay = 2ms # default vacuum cost delay for
# autovacuum, in milliseconds;
# -1 means use vacuum_cost_delay
#autovacuum_vacuum_cost_limit = -1  # default vacuum cost limit for
# autovacuum, -1 means use
# vacuum_cost_limit
#------------------------------------------------------------------------------
# CLIENT CONNECTION DEFAULTS
#------------------------------------------------------------------------------
# - Statement Behavior -
#client_min_messages = notice       # values in order of decreasing detail:
#   debug5
#   debug4
#   debug3
#   debug2
#   debug1
#   log
#   notice
#   warning
#   error
#search_path = '"$user", public'    # schema names
#row_security = on
#default_tablespace = ''        # a tablespace name, '' uses the default
#temp_tablespaces = ''          # a list of tablespace names, '' uses
# only default tablespace
#check_function_bodies = on
#default_transaction_isolation = 'read committed'
#default_transaction_read_only = off
#default_transaction_deferrable = off
#session_replication_role = 'origin'
#statement_timeout = 0          # in milliseconds, 0 is disabled
#lock_timeout = 0           # in milliseconds, 0 is disabled
#idle_in_transaction_session_timeout = 0    # in milliseconds, 0 is disabled
#vacuum_freeze_min_age = 50000000
#vacuum_freeze_table_age = 150000000
#vacuum_multixact_freeze_min_age = 5000000
#vacuum_multixact_freeze_table_age = 150000000
#vacuum_cleanup_index_scale_factor = 0.1    # fraction of total number of tuples
# before index cleanup, 0 always performs
# index cleanup
#bytea_output = 'hex'           # hex, escape
#xmlbinary = 'base64'
#xmloption = 'content'
#gin_fuzzy_search_limit = 0
#gin_pending_list_limit = 4MB
# - Locale and Formatting -
#datestyle = 'iso, mdy'
#intervalstyle = 'postgres'
#timezone = 'GMT'
#timezone_abbreviations = 'Default'     # Select the set of available time zone
# abbreviations.  Currently, there are
#   Default
#   Australia (historical usage)
#   India
# You can create your own file in
# share/timezonesets/.
#extra_float_digits = 1         # min -15, max 3; any value >0 actually
# selects precise output mode
#client_encoding = sql_ascii        # actually, defaults to database
# encoding
# These settings are initialized by initdb, but they can be changed.
#lc_messages = 'C'          # locale for system error message
# strings
#lc_monetary = 'C'          # locale for monetary formatting
#lc_numeric = 'C'           # locale for number formatting
#lc_time = 'C'              # locale for time formatting
# default configuration for text search
#default_text_search_config = 'pg_catalog.simple'
# - Shared Library Preloading -
#shared_preload_libraries = ''  # (change requires restart)
#local_preload_libraries = ''
#session_preload_libraries = ''
#jit_provider = 'llvmjit'       # JIT library to use
# - Other Defaults -
#dynamic_library_path = '$libdir'
#------------------------------------------------------------------------------
# LOCK MANAGEMENT
#------------------------------------------------------------------------------
#deadlock_timeout = 1s
#max_locks_per_transaction = 64     # min 10
# (change requires restart)
#max_pred_locks_per_transaction = 64    # min 10
# (change requires restart)
#max_pred_locks_per_relation = -2   # negative values mean
# (max_pred_locks_per_transaction
#  / -max_pred_locks_per_relation) - 1
#max_pred_locks_per_page = 2            # min 0
#------------------------------------------------------------------------------
# VERSION AND PLATFORM COMPATIBILITY
#------------------------------------------------------------------------------
# - Previous PostgreSQL Versions -
#array_nulls = on
#backslash_quote = safe_encoding    # on, off, or safe_encoding
#escape_string_warning = on
#lo_compat_privileges = off
#operator_precedence_warning = off
#quote_all_identifiers = off
#standard_conforming_strings = on
#synchronize_seqscans = on
# - Other Platforms and Clients -
#transform_null_equals = off
#------------------------------------------------------------------------------
# ERROR HANDLING
#------------------------------------------------------------------------------
#exit_on_error = off            # terminate session on any error?
#restart_after_crash = on       # reinitialize after backend crash?
#data_sync_retry = off          # retry or panic on failure to fsync
# data?
# (change requires restart)
#------------------------------------------------------------------------------
# CONFIG FILE INCLUDES
#------------------------------------------------------------------------------
# These options allow settings to be loaded from files other than the
# default postgresql.conf.
#include_dir = 'conf.d'         # include files ending in '.conf' from
# directory 'conf.d'
#include_if_exists = 'exists.conf'  # include file only if it exists
#include = 'special.conf'       # include file
#------------------------------------------------------------------------------
# CUSTOMIZED OPTIONS
#------------------------------------------------------------------------------
# Add settings for extensions here

Izay ihany, azonao atao ny manomboka container miaraka amin'ny baiko docker-compose up -d. Na amin'ny console misaraka miaraka amin'ny baiko docker-compose up.

Noho izany, napetraka ny fonosana, natomboka ny angon-drakitra, ny hany sisa tavela dia ny fifaneraserana amin'izy ireo. Mba hanaovana izany dia mila manampy ity rakitra manaraka ity amin'ny fototry ny tetikasa ianao: ormconfig.js:

ormconfig.js

const process = require('process');
const username = process.env.POSTGRES_USER || "postgres";
const password = process.env.POSTGRES_PASSWORD || "example";
module.exports = {
"type": "postgres",
"host": "localhost",
"port": 5432,
username,
password,
"database": "postgres",
"synchronize": true,
"dropSchema": false,
"logging": true,
"entities": [__dirname + "/src/**/*.entity.ts", __dirname + "/dist/**/*.entity.js"],
"migrations": ["migrations/**/*.ts"],
"subscribers": ["subscriber/**/*.ts", "dist/subscriber/**/.js"],
"cli": {
"entitiesDir": "src",
"migrationsDir": "migrations",
"subscribersDir": "subscriber"
}
}

Ity fandrindrana ity dia hampiasaina amin'ny cli typeorm.

Andeha hojerentsika amin'ny antsipiriany bebe kokoa ity fanamafisana ity. Ao amin'ny andalana 3 sy 4 dia mahazo ny solon'anarana sy ny tenimiafina avy amin'ny fari-piainan'ny tontolo iainana. Mety izany rehefa manana tontolo maro ianao (dev, stage, prod, sns). Amin'ny alàlan'ny default, ny solonanarana dia postgres ary ny tenimiafina dia ohatra. Ny sisa amin'ny config dia tsinontsinona, noho izany dia hifantoka amin'ireo mari-pamantarana mahaliana indrindra isika:

• synchronize - Manondro raha tokony ho noforonina ho azy ny schema database rehefa manomboka ny fampiharana. Mitandrema amin'ity safidy ity ary aza ampiasaina amin'ny famokarana, raha tsy izany dia ho very data ianao. Ity safidy ity dia mety amin'ny famolavolana sy ny debugging fampiharana. Ho solon'ity safidy ity dia azonao ampiasaina ny baiko schema:sync avy amin'ny CLI TypeORM.
• dropSchema - avereno indray ny schema isaky ny misy fifandraisana. Tahaka ny teo aloha, ity safidy ity dia tokony hampiasaina mandritra ny fampandrosoana sy ny debugging ny fampiharana.
• entity - izay lalana hitadiavana famaritana ny modely. Mariho fa ny fikarohana amin'ny saron-tava dia tohana.
• cli.entitiesDir dia ny lahatahiry izay tokony hotehirizina amin'ny alàlan'ny default ny modely noforonina avy amin'ny TypeORM CLI.

Mba hahafahantsika mampiasa ny endri-javatra rehetra an'ny TypeORM ao amin'ny fampiharana Nest antsika, dia mila manafatra ny maody isika TypeOrmModule в AppModule. Ireo. NY AppModule dia ho toy izao:

app.module.ts

import { Module } from '@nestjs/common';
import { AppController } from './app.controller';
import { AppService } from './app.service';
import { TypeOrmModule } from '@nestjs/typeorm';
import * as process from "process";
const username = process.env.POSTGRES_USER || 'postgres';
const password = process.env.POSTGRES_PASSWORD || 'example';
@Module({
imports: [
TypeOrmModule.forRoot({
type: 'postgres',
host: 'localhost',
port: 5432,
username,
password,
database: 'postgres',
entities: [__dirname + '/**/*.entity{.ts,.js}'],
synchronize: true,
}),
],
controllers: [AppController],
providers: [AppService],
})
export class AppModule {}

Araka ny efa hitanao, ny fomba forRoot ny fandrindrana mitovy amin'ny fiasana amin'ny angon-drakitra dia nafindra toy ny ao amin'ny rakitra ormconfig.ts

Mijanona ny fikasihana farany - ampio asa maromaro hiasa amin'ny TypeORM ao amin'ny package.json. Ny zava-misy dia ny CLI dia voasoratra amin'ny javascript ary mandeha amin'ny tontolo nodejs. Na izany aza, ny modely sy ny fifindra-monina rehetra dia hosoratana amin'ny sora-tanana. Noho izany, ilaina ny mandika ny fifindra-monina sy ny modely alohan'ny hampiasana ny CLI. Mba hanaovana izany dia mila ny fonosana ts-node isika:

yarn add -D ts-node

Aorian'izay, ampio ny baiko ilaina amin'ny package.json:

"typeorm": "ts-node -r tsconfig-paths/register ./node_modules/typeorm/cli.js",
"migration:generate": "yarn run typeorm migration:generate -n",
"migration:create": "yarn run typeorm migration:create -n",
"migration:run": "yarn run typeorm migration:run"

Ny baiko voalohany, typeorm, dia manampy fonosana ts-node hampandeha ny TypeORM cli. Ny baiko sisa dia hitsin-dàlana mora ampiasainao, amin'ny maha-mpamorona anao, saika isan'andro:
migration:generate - mamorona fifindra-monina mifototra amin'ny fanovana ny maodely.
migration:create - mamorona fifindra-monina foana.
migration:run - manomboka fifindra-monina.
Eny, izany izao, nampiana ireo fonosana ilaina izahay, nanamboatra ny rindranasa hiara-miasa amin'ny angon-drakitra na avy amin'ny cli na avy amin'ny fampiharana mihitsy, ary nanangana ny DBMS ihany koa. Fotoana hanampiana lojika amin'ny fampiharanay izao.

Fametrahana fonosana hamoronana CRUD

Amin'ny fampiasana ny Nest ihany, dia afaka mamorona API ahafahanao mamorona, mamaky, manavao, ary mamafa enti-manana. Ity vahaolana ity dia ho malefaka araka izay azo atao, fa amin'ny toe-javatra sasany dia ho tafahoatra. Ohatra, raha mila mamorona prototype haingana ianao, dia azonao atao matetika ny manao sorona ny fahafaha-manatsara ny hafainganam-pandehan'ny fampandrosoana. Firafitra maro no manome fampiasa amin'ny famokarana CRUD amin'ny alalan'ny famaritana ny maodely angon-drakitra an'ny orinasa iray. Ary tsy maningana ny Nest! Ity fampiasa ity dia omen'ny fonosana @nestjsx/crud. Tena mahaliana ny fahaizany:

• fametrahana mora sy fanamafisana;
• fahaleovantena DBMS;
• fiteny fanontanina mahery vaika manana fahafahana manivana, mametaka pejy, mandamina, mameno ny fifandraisana ary ireo singa misy akany, caching, sns.;
• fonosana amin'ny famoronana fangatahana eo amin'ny front-end;
• mora override ny fomba fanaraha-maso;
• config kely;
• fanohanana antontan-taratasy swagger.

Ny fiasa dia mizara ho fonosana maromaro:

• @nestjsx/crud - ny fonosana fototra omen'ny mpanao haingon-trano Crud() ho an'ny famoronana lalana, fanamafisana ary fanamarinana;
• @nestjsx/crud-request - fonosana izay manome mpanorina fanontaniana / parser ampiasaina amin'ny lafiny anoloana;
• @nestjsx/crud-typeorm - fonosana ho an'ny fampidirana miaraka amin'ny TypeORM, manome ny serivisy TypeOrmCrudService fototra miaraka amin'ny fomba CRUD amin'ny fiaraha-miasa amin'ireo sampana ao amin'ny tahiry.

Amin'ity lesona ity dia mila fonosana isika akaninyjsx/crud ary akaninyjsx/crud-typeorm. Voalohany, andeha hojerentsika izy ireo

yarn add @nestjsx/crud class-transformer class-validator

entana class-transformer и class-validator amin'ity fampiharana ity dia takiana amin'ny filazalazana ny fitsipika momba ny fanovana ireo ohatra modely sy ny fanamarinana ireo fangatahana miditra. Ireo fonosana ireo dia avy amin'ny mpanoratra iray ihany, noho izany dia mitovy ny interface.

Fampiharana mivantana ny CRUD

Haka lisitr'ireo mpampiasa izahay ho ohatra modely. Ny mpampiasa dia hanana ireto sehatra manaraka ireto: id, username, displayName, email. id - saha mitombo mandeha ho azy, email и username - saha tsy manam-paharoa. Tsotra izany! Ny hany sisa tavela dia ny fampiharana ny hevitray amin'ny endrika fampiharana Nest.
Voalohany dia mila mamorona module ianao users, izay ho tompon'andraikitra amin'ny fiaraha-miasa amin'ireo mpampiasa. Andao hampiasa ny cli avy amin'ny NestJS ary tanteraho ny baiko ao amin'ny lahatahiry fototry ny tetikasantsika nest g module users.

ireo mpampiasa module nest g

dmitrii@dmitrii-HP-ZBook-17-G3:~/projects/nest-rest git:(master*)$ nest g module users
CREATE /src/users/users.module.ts (82 bytes)
UPDATE /src/app.module.ts (312 bytes)

Amin'ity module ity dia hanampy lahatahiry entity isika, izay hananantsika ny modely amin'ity module ity. Indrindra indrindra, andao ampiana eto ny rakitra user.entity.ts miaraka amin'ny famaritana ny modely mpampiasa:

user.entity.ts

import { Column, Entity, PrimaryGeneratedColumn } from 'typeorm';
@Entity()
export class User {
@PrimaryGeneratedColumn()
id: string;
@Column({unique: true})
email: string;
@Column({unique: true})
username: string;
@Column({nullable: true})
displayName: string;
}

Mba hahafahan'ity modely ity ho "hita" amin'ny fampiharana ataontsika dia ilaina izany ao amin'ny module UsersModule manafatra TypeOrmModule ireto votoaty manaraka ireto:

users.module.ts

import { Module } from '@nestjs/common';
import { UsersController } from './controllers/users/users.controller';
import { UsersService } from './services/users/users.service';
import { TypeOrmModule } from '@nestjs/typeorm';
import { User } from './entities/user.entity';
@Module({
controllers: [UsersController],
providers: [UsersService],
imports: [
TypeOrmModule.forFeature([User])
]
})
export class UsersModule {}

Izany hoe eto izahay manafatra TypeOrmModule, izay ho toy ny paramètre methode forFeature Manondro lisitr'ireo modely mifandraika amin'ity module ity izahay.

Ny hany sisa tavela dia ny mamorona ny singa mifandraika amin'izany ao amin'ny tahiry. Ny rafitra fifindra-monina dia miasa ho an'ireo tanjona ireo. Mba hamoronana fifindra-monina mifototra amin'ny fiovan'ny modely dia mila manatanteraka ny baiko ianao npm run migration:generate -- CreateUserTable:

Lohateny spoiler

$ npm run migration:generate -- CreateUserTable
Migration /home/dmitrii/projects/nest-rest/migrations/1563346135367-CreateUserTable.ts has been generated successfully.
Done in 1.96s.

Tsy voatery nanoratra ny fifindra-monina tamin'ny tanana izahay, ny zava-drehetra dia niseho tamin'ny fomba mahagaga. Tsy mahagaga ve izany! Tsy izay ihany anefa. Andeha hojerentsika ny rakitra fifindra-monina noforonina:

1563346135367-CreateUserTable.ts

import {MigrationInterface, QueryRunner} from "typeorm";
export class CreateUserTable1563346816726 implements MigrationInterface {
public async up(queryRunner: QueryRunner): Promise<any> {
await queryRunner.query(`CREATE TABLE "user" ("id" SERIAL NOT NULL, "email" character varying NOT NULL, "username" character varying NOT NULL, "displayName" character varying, CONSTRAINT "UQ_e12875dfb3b1d92d7d7c5377e22" UNIQUE ("email"), CONSTRAINT "UQ_78a916df40e02a9deb1c4b75edb" UNIQUE ("username"), CONSTRAINT "PK_cace4a159ff9f2512dd42373760" PRIMARY KEY ("id"))`);
}
public async down(queryRunner: QueryRunner): Promise<any> {
await queryRunner.query(`DROP TABLE "user"`);
}
}

Araka ny hitanao, tsy ny fomba fanombohana ny fifindra-monina ihany no noforonina ho azy, fa ny fomba hamerenana azy koa. Fantastic!
Ny hany sisa tavela dia ny famoahana ity fifindra-monina ity. Izany dia atao amin'ny baiko manaraka:

npm run migration:run.

Izay no izy, nifindra tany amin'ny angon-drakitra ny fanovana schema.
Manaraka izany dia hamorona serivisy iray izay tompon'andraikitra amin'ny fiaraha-miasa amin'ny mpampiasa sy handova azy TypeOrmCrudService. Ny fitehirizana ny sampan-draharaha liana dia tsy maintsy ampitaina amin'ny mari-pamantarana ny mpanorina ray aman-dreny, amin'ny tranga misy antsika User repository.

users.service.ts

import { Injectable } from '@nestjs/common';
import { TypeOrmCrudService } from '@nestjsx/crud-typeorm';
import { User } from '../../entities/user.entity';
import { InjectRepository } from '@nestjs/typeorm';
import { Repository } from 'typeorm';
@Injectable()
export class UsersService extends TypeOrmCrudService<User>{
constructor(@InjectRepository(User) usersRepository: Repository<User>){
super(usersRepository);
}
}

Mila an'ity serivisy ity izahay ao amin'ny controller users. Mba hamoronana controller dia midira ao amin'ny console nest g controller users/controllers/users

nest g mpifehy mpampiasa/mpifehy/mpampiasa

dmitrii@dmitrii-HP-ZBook-17-G3:~/projects/nest-rest git:(master*)$ nest g controller users/controllers/users
CREATE /src/users/controllers/users/users.controller.spec.ts (486 bytes)
CREATE /src/users/controllers/users/users.controller.ts (99 bytes)
UPDATE /src/users/users.module.ts (188 bytes)

Andeha hosokafantsika ity mpanara-maso ity ary ovaina mba hanampiana ody kely akaninyjsx/crud. Isaky ny kilasy UsersController Andeha asiana haingo toy izao:

@Crud({
model: {
type: User
}
})

Crud dia haingon-trano izay manampy ny mpanara-maso ny fomba ilaina amin'ny fiasana amin'ny modely. Ny karazana modely dia aseho amin'ny saha model.type fanamboarana haingon-trano.
Ny dingana faharoa dia ny fampiharana ny interface CrudController<User>. Toy izao ny code controller "Assembled":

import { Controller } from '@nestjs/common';
import { Crud, CrudController } from '@nestjsx/crud';
import { User } from '../../entities/user.entity';
import { UsersService } from '../../services/users/users.service';
@Crud({
model: {
type: User
}
})
@Controller('users')
export class UsersController implements CrudController<User>{
constructor(public service: UsersService){}
}

Ary izany rehetra izany! Ankehitriny ny mpanara-maso dia manohana ny andiana hetsika manontolo miaraka amin'ny modely! Aza mino ahy? Andao hanandrana ny fampiharana ataontsika!

Mamorona Script Query ao amin'ny TestMace

Mba hitsapana ny serivisinay dia hampiasa IDE izahay hiasa amin'ny API TestMace. Nahoana no TestMace? Raha oharina amin'ny vokatra mitovy amin'izany, dia manana tombony manaraka ireto:

• asa mahery miaraka amin'ny variables. Amin'izao fotoana izao, misy karazana varimbazaha maromaro, izay samy manana ny anjara toerany manokana: ny fari-piainana naorina, ny dynamic variable, ny tontolo iainana. Ny fari-piainana tsirairay dia an'ny node iray misy fanohanana ny mekanika lova;
• Mamorona script tsy misy fandaharana. Horesahina eto ambany izany;
• endrika azo vakin'ny olombelona izay ahafahanao mitahiry ny tetikasa amin'ny rafitra fanaraha-maso dikan-teny;
• autocompletion, fanasongadinana syntax, fanasongadinana sanda miovaova;
• Fanohanana famaritana API miaraka amin'ny fahafahana manafatra avy amin'ny Swagger.

Andeha isika hanomboka ny mpizara amin'ny baiko npm start ary andramo miditra amin'ny lisitry ny mpampiasa. Ny lisitr'ireo mpampiasa, raha jerena amin'ny alàlan'ny fanamafisana ny controller, dia azo alaina amin'ny url localhost:3000/users. Andao hanao fangatahana amin'ity url ity.
Rehefa vita ny TestMace dia afaka mahita interface toy izao ianao:

Eo an-tampony havia dia hazo tetikasa misy fotony tetikasa. Andao hiezaka hamorona ny fangatahana voalohany hahazoana lisitry ny mpampiasa. Ho an'izany dia hamorona isika RequestStep node Izany dia atao ao amin'ny menio contexte amin'ny node Project Ampio node -> RequestStep.

Ao amin'ny saha URL, apetaho localhost:3000/users ary tanteraho ny fangatahana. Hahazo kaody 200 miaraka amin'ny laharan-tariby foana isika ao amin'ny vatan'ny valiny. Azo takarina izany, tsy mbola nampiana olona izahay.
Andao hamorona script izay ahitana ireto dingana manaraka ireto:

1. famoronana mpampiasa;
2. fangatahana ny id an'ilay mpampiasa vao noforonina;
3. famafana amin'ny alàlan'ny ID mpampiasa noforonina tamin'ny dingana 1.

Andeha àry. Ho fanamorana, andao hamorona node toy ny lahatahiry. Amin'ny ankapobeny, ity dia lahatahiry iray izay hamonjena ny script manontolo. Mba hamoronana node Folder, safidio ny Project avy amin'ny menio contexte amin'ny node Ampio node -> Folder. Andao hiantso ny node check-create. Ao anaty node check-create Andao hamorona ny fangatahanay voalohany hamorona mpampiasa. Andao hiantso ny node vao noforonina mamorona-mpampiasa. Izany hoe, amin'izao fotoana izao ny hierarchy node dia ho toy izao:

Andeha ho any amin'ny tabilao misokatra mamorona-mpampiasa node. Ampidiro ireto paramètre manaraka ireto ho an'ny fangatahana:

• Karazana fangatahana - POST
• URL - localhost:3000/users
• Vatana - JSON misy sanda {"email": "[email protected]", "displayName": "New user", "username": "user"}

Andeha hotanterahina izany fangatahana izany. Ny fampiharana anay dia milaza fa ny rakitra dia noforonina.

Andeha hojerentsika io zava-misy io. Mba hahafahana miasa miaraka amin'ny id an'ny mpampiasa noforonina amin'ny dingana manaraka dia tsy maintsy hotehirizina io paramètre io. Ny mekanika dia tonga lafatra amin'izany. miovaova miovaova. Andeha hojerentsika ny fomba hiarahana miasa amin'izy ireo. Ao amin'ny tabilao voasakana amin'ny valiny, eo akaikin'ny node id amin'ny menu context, safidio ilay entana Hiverina any amin'ny variable. Ao amin'ny boaty fifanakalozan-kevitra dia tsy maintsy mametraka ireto parameter manaraka ireto ianao:

• node — izay amin'ireo razambe no mamorona fari-piainana mavitrika. Andeha isika hisafidy check-create
• Anarana voamarina - ny anaran'io faribolana io. Andeha hiantso userId.

Toy izao ny fizotry ny famoronana faribolana dynamique:

Ankehitriny, isaky ny tanterahana ity fangatahana ity dia havaozina ny sandan'ny fari-piainana mavitrika. Ary satria dynamic variables manohana ny mekanisma ny lova ambaratongam-pahefana, miovaova userId dia ho hita amin'ny taranaka check-create node amin'ny ambaratonga rehetra.
Ity faribolana ity dia hahasoa antsika amin'ny fangatahana manaraka. Izany hoe, hangataka ny mpampiasa vao noforonina izahay. Toy ny zanaky ny node check-create hamorona fangatahana izahay fanamarinana-raha misy miaraka amin'ny parameter url mitovy localhost:3000/users/${$dynamicVar.userId}. Jereo ny famolavolana ${variable_name} izany dia mahazo ny sandan'ny variable. SATRIA Manana fari-piainana mavitrika isika, ka raha te hahazo izany ianao dia mila miditra amin'ilay zavatra $dynamicVar, izany hoe miditra tanteraka amin'ny fari-piainana mavitrika userId dia ho tahaka izao ${$dynamicVar.userId}. Andeha hotanterahina ny fangatahana ary ho azo antoka fa nangatahana tsara ny angona.
Ny dingana farany sisa dia ny fangatahana famafana. Mila izany isika tsy hanamarina ny fiasan'ny famafana fotsiny, fa koa, raha lazaina, hanadio ny tenantsika ao amin'ny tahiry, satria Ny saha mailaka sy solonanarana dia miavaka. Noho izany, ao amin'ny check-create node dia hamorona fangatahana famafana-mpampiasa miaraka amin'ireto marika manaraka ireto

• Karazana fangatahana - DELETE
• URL - localhost:3000/users/${$dynamicVar.userId}

Andao hanomboka. Miandry izahay. Ankafizinay ny vokatra)

Eny, afaka mampandeha an'ity script ity isika amin'ny fotoana rehetra. Mba hampandehanana ny script dia mila misafidy avy amin'ny menu context ianao check-create zavatra node Run.

Ny nodes ao amin'ny script dia hotanterahina tsirairay
Azonao atao ny mitahiry ity script ity amin'ny tetikasanao amin'ny alàlan'ny fandehanana File -> Save project.

famaranana

Ny endri-javatra rehetra amin'ny fitaovana ampiasaina dia tsy mety amin'ny endrika amin'ity lahatsoratra ity. Raha ny tena meloka - ny fonosana akaninyjsx/crud - mbola tsy fantatra ireto lohahevitra manaraka ireto:

• fanamarinana manokana sy fanovana modely;
• fiteny fanontanina mahery vaika sy ny fampiasana azy tsara eo anoloana;
• fanavaozana sy fampidirana fomba vaovao amin'ny fanaraha-maso crud;
• fanohanana swagger;
• fitantanana caching.

Na izany aza, na dia izay voalaza ao amin'ny lahatsoratra aza dia ampy hahatakarana fa na ny rafitra orinasa toy ny NestJS aza dia manana fitaovana ho an'ny prototyping fampiharana haingana. Ary IDE mahafinaritra toy izany TestMace mamela anao hihazona ny hafainganam-pandeha nomena.

Kaody loharano ho an'ity lahatsoratra ity, miaraka amin'ny tetikasa TestMace, hita ao amin'ny tahiry https://github.com/TestMace/nest-rest. Hanokatra tetikasa TestMace ataovy ao anaty app fotsiny File -> Open tetikasa.

Source: www.habr.com