Op it stuit is de REST API in standert wurden foar ûntwikkeling fan webapplikaasjes, wêrtroch ûntwikkeling kin wurde ferdield yn ûnôfhinklike dielen. Ferskate populêre kaders lykas Angular, React, Vue en oaren wurde op it stuit brûkt foar UI. Backend-ûntwikkelders kinne kieze út in breed ferskaat oan talen en kaders. Hjoed soe ik graach prate oer sa'n ramt as NestJS. Wy binne yn TestMace Wy brûke it aktyf foar ynterne projekten. Mei help fan nêst en pakket @nestjsx/crud, sille wy in ienfâldige CRUD-applikaasje meitsje.

Wêrom NestJS

Koartlyn binne nochal in protte backend-frames ferskynd yn 'e JavaScript-mienskip. En as se yn termen fan funksjonaliteit ferlykbere mooglikheden leverje as Nest, dan wint it yn ien ding perfoarst - dit is de arsjitektuer. De folgjende NestJS-funksjes kinne jo yndustriële applikaasjes meitsje en skaalûntwikkeling meitsje foar grutte teams:

• mei TypeScript as de wichtichste ûntwikkelingstaal. Hoewol NestJS JavaScript stipet, kin guon funksjonaliteit net wurkje, benammen as wy it oer pakketten fan tredden prate;
• de oanwêzigens fan in DI-container, wêrtroch jo loskeppele komponinten kinne meitsje;
• De funksjonaliteit fan it ramt sels is ferdield yn ûnôfhinklike útwikselbere komponinten. Bygelyks, ûnder de kap as ramt kin it brûkt wurde as ekspresjeen fêstigje, om te wurkjen mei de databank, nêst út 'e doaze jout bindingen oan typorm, mongoose, ferfolch;
• NestJS is platfoarm agnostyk en stipet REST, GraphQL, Websockets, gRPC, ensfh.

It ramt sels is ynspirearre troch it Angular frontend framework en hat konseptueel in protte mienskiplik mei.

NestJS ynstallearje en it projekt ynsette

Nest befettet in pakket nêst/cli, wêrtroch jo in basisapplikaasjekader fluch kinne ynsette. Litte wy dit pakket wrâldwiid ynstallearje:

npm install --global @nest/cli

Nei ynstallaasje sille wy it basiskader fan ús applikaasje generearje mei de namme nest-rest. Dit wurdt dien mei it kommando nest new nest-rest.

nêst nij nêst-rêst

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

Wy sille garen kieze as ús pakketbehearder.
Op dit punt kinne jo de tsjinner begjinne mei it kommando npm start en gean nei it adres http://localhost:3000 jo kinne de haadside sjen. Dit is lykwols net wêrom wy hjir sammele binne en wy geane troch.

It opsetten fan wurk mei de databank

Ik keas PostrgreSQL as de DBMS foar dit artikel. D'r is gjin skeel oer smaak; neffens my is dit de meast folwoeksen DBMS, mei alle nedige mooglikheden. Lykas al neamd, biedt Nest yntegraasje mei ferskate pakketten om te wurkjen mei databases. Omdat Sûnt myn kar foel op PostgreSQL, soe it logysk wêze om TypeORM as ORM te kiezen. Litte wy de nedige pakketten ynstallearje foar yntegraasje mei de databank:

yarn add typeorm @nestjs/typeorm pg

Yn oarder, wêrfoar is elk pakket nedich:

1. typeorm - in pakket direkt fan 'e ORM sels;
2. @nestjs/typeorm - TypeORM-pakket foar NestJS. Foeget modules ta foar ymportearjen yn projektmodules, lykas ek in set helpdekorateurs;
3. pg - stjoerprogramma foar wurkjen mei PostgreSQL.

Okee, de pakketten binne ynstalleare, no moatte jo de database sels starte. Om de databank yn te setten, sil ik docker-compose.yml brûke mei de folgjende ynhâld:

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

Sa't jo sjen kinne, konfigurearret dit bestân de lansearring fan 2 konteners:

1. db is in kontener dy't direkt de databank befettet. Yn ús gefal wurdt postgresql ferzje 11.2 brûkt;
2. adminer-databasebehearder. Biedt in webynterface foar it besjen en behearen fan de databank.

Om te wurkjen mei tcp-ferbiningen haw ik de folgjende konfiguraasje tafoege.

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

Dat is alles, jo kinne konteners begjinne mei it kommando docker-compose up -d. Of yn in aparte konsole mei it kommando docker-compose up.

Dat, de pakketten binne ynstalleare, de databank is lansearre, alles wat oerbliuwt is har freonen mei elkoar te meitsjen. Om dit te dwaan, moatte jo it folgjende bestân tafoegje oan 'e projektroot: 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"
}
}

Dizze konfiguraasje sil brûkt wurde foar cli typeorm.

Litte wy nei dizze konfiguraasje yn mear detail sjen. Op rigels 3 en 4 krije wy de brûkersnamme en wachtwurd fan de omjouwingsfariabelen. Dit is handich as jo ferskate omjouwings hawwe (dev, poadium, prod, ensfh.). Standert is de brûkersnamme postgres en it wachtwurd is foarbyld. De rest fan 'e konfiguraasje is triviaal, dus wy sille allinich rjochtsje op de meast nijsgjirrige parameters:

• syngronisearje - Jout oan oft it databankskema automatysk oanmakke wurde moat as de applikaasje begjint. Wês foarsichtich mei dizze opsje en brûk it net yn produksje, oars sille jo gegevens ferlieze. Dizze opsje is handich by it ûntwikkeljen en debuggen fan in applikaasje. As alternatyf foar dizze opsje kinne jo it kommando brûke schema:sync fan CLI TypeORM.
• dropSchema - reset it skema elke kear as in ferbining wurdt oprjochte. Krekt as de foarige, moat dizze opsje allinich brûkt wurde tidens de ûntwikkeling en debuggen fan 'e applikaasje.
• entiteiten - hokker paden om te sykjen nei beskriuwingen fan modellen. Tink derom dat sykjen op masker wurdt stipe.
• cli.entitiesDir is de map wêr't modellen makke út de TypeORM CLI standert moatte wurde opslein.

Om ús alle funksjes fan TypeORM yn ús Nest-applikaasje te brûken, moatte wy de module ymportearje TypeOrmModule в AppModule. Dy. dyn AppModule sil der sa útsjen:

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 {}

As jo ​​miskien hawwe opfallen, de metoade forRoot deselde konfiguraasje foar wurkjen mei de databank wurdt oerdroegen as yn de ormconfig.ts triem

De lêste touch bliuwt - foegje ferskate taken ta foar wurkjen mei TypeORM yn package.json. It feit is dat de CLI is skreaun yn javascript en rint yn 'e nodejs-omjouwing. Al ús modellen en migraasjes sille lykwols yn typeskrift skreaun wurde. Dêrom is it nedich om ús migraasjes en modellen te transpilearjen foardat jo de CLI brûke. Hjirfoar hawwe wy it ts-node-pakket nedich:

yarn add -D ts-node

Foegje dêrnei de nedige kommando's ta oan 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"

It earste kommando, typeorm, foeget in ts-node wrapper ta om de TypeORM cli út te fieren. De oerbleaune kommando's binne handige fluchtoetsen dy't jo, as ûntwikkelder, hast alle dagen sille brûke:
migration:generate - it meitsjen fan migraasjes basearre op feroaringen yn jo modellen.
migration:create - it meitsjen fan in lege migraasje.
migration:run - it lansearjen fan migraasjes.
No, dat is it no, wy hawwe de nedige pakketten tafoege, de applikaasje konfigureare om te wurkjen mei de databank sawol fan 'e cli as fan' e applikaasje sels, en ek de DBMS lansearre. It is tiid om logika ta te foegjen oan ús applikaasje.

Ynstallaasje fan pakketten foar it meitsjen fan CRUD

Mei allinich Nest kinne jo in API oanmeitsje wêrmei jo in entiteit kinne oanmeitsje, lêze, bywurkje en wiskje. Dizze oplossing sil sa fleksibel mooglik wêze, mar yn guon gefallen sil it oerstallich wêze. As jo ​​​​bygelyks fluch in prototype moatte oanmeitsje, kinne jo faaks fleksibiliteit opofferje foar snelheid fan ûntwikkeling. In protte kaders jouwe funksjonaliteit foar it generearjen fan CRUD troch it gegevensmodel fan in bepaalde entiteit te beskriuwen. En Nest is gjin útsûndering! Dizze funksjonaliteit wurdt levere troch it pakket @nestjsx/crud. Syn mooglikheden binne tige nijsgjirrich:

• maklike ynstallaasje en konfiguraasje;
• DBMS ûnôfhinklikens;
• krêftige query-taal mei de mooglikheid om te filterjen, paginearjen, sortearjen, laden relaasjes en geneste entiteiten, caching, ensfh.
• pakket foar it generearjen fan oanfragen op 'e front-end;
• maklik oerskriuwen fan kontrôlemetoaden;
• lytse konfiguraasje;
• swagger dokumintaasje stipe.

De funksjonaliteit is ferdield yn ferskate pakketten:

• @nestjsx/crud - it basispakket dat de dekorateur jout Crud() foar rûtegeneraasje, konfiguraasje en falidaasje;
• @nestjsx/crud-request - in pakket dat in query builder / parser leveret foar gebrûk oan 'e frontend-kant;
• @nestjsx/crud-typeorm - in pakket foar yntegraasje mei TypeORM, it leverjen fan de basis TypeOrmCrudService-tsjinst mei CRUD-metoaden foar wurkjen mei entiteiten yn 'e databank.

Yn dizze tutorial sille wy pakketten nedich hawwe nêstjsx/crud en nêstjsx/crud-typeorm. Earst litte wy se pleatse

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

Pakketten klasse-transformator и klasse-validator yn dizze applikaasje binne ferplichte foar in ferklearjende beskriuwing fan de regels foar transforming model eksimplaren en falidearjen ynkommende fersiken, respektivelik. Dizze pakketten binne fan deselde auteur, dus de ynterfaces binne ferlykber.

Direkte ymplemintaasje fan CRUD

Wy sille in list mei brûkers nimme as foarbyldmodel. Brûkers sille de folgjende fjilden hawwe: id, username, displayName, email. id - fjild foar auto-inkrementearjen, email и username - unike fjilden. It is ienfâldich! Alles wat oerbliuwt is ús idee út te fieren yn 'e foarm fan in Nest-applikaasje.
Earst moatte jo in module oanmeitsje users, wa sil wêze ferantwurdlik foar it wurkjen mei brûkers. Litte wy de cli fan NestJS brûke en it kommando útfiere yn 'e rootmap fan ús projekt nest g module users.

nêst g module brûkers

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)

Yn dizze module sille wy in map mei entiteiten tafoegje, wêr't wy de modellen fan dizze module sille hawwe. Lit ús hjir benammen it bestân user.entity.ts tafoegje mei in beskriuwing fan it brûkersmodel:

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;
}

Om dit model te "sjoen" troch ús applikaasje, is it nedich yn 'e module UsersModule ymport TypeOrmModule de folgjende ynhâld:

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 {}

Dat is, hjir ymportearje wy TypeOrmModule, wêr as in metoade parameter forFeature Wy jouwe in list fan modellen yn ferbân mei dizze module.

Alles wat oerbliuwt is de oerienkommende entiteit yn 'e databank te meitsjen. It migraasjemeganisme tsjinnet foar dizze doelen. Om in migraasje te meitsjen basearre op feroaringen yn modellen, moatte jo it kommando útfiere npm run migration:generate -- CreateUserTable:

spoiler titel

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

Wy hoegden de migraasje net mei de hân te skriuwen, alles barde magysk. Is dit net in wûnder! Dat is lykwols net alles. Litte wy ris nei it oanmakke migraasjebestân sjen:

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"`);
}
}

Sa't jo sjen kinne, waard net allinich de metoade foar it starten fan 'e migraasje automatysk oanmakke, mar ek de metoade foar it weromrollen. Fantastysk!
Alles wat oerbliuwt is dizze migraasje út te rollen. Dit wurdt dien mei it folgjende kommando:

npm run migration:run.

Dat is it, no binne de skemawizigingen migrearre nei de database.
Folgjende, wy sille meitsje in tsjinst dy't sil wêze ferantwurdlik foar it wurkjen mei brûkers en ervje it fan TypeOrmCrudService. It repository fan 'e entiteit fan belang moat wurde trochjûn oan' e parameter fan 'e âlderkonstruktor, yn ús gefal 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);
}
}

Wy sille dizze tsjinst nedich wêze yn 'e controller users. Om in controller te meitsjen, typ de konsole yn nest g controller users/controllers/users

nest g controller brûkers / controllers / brûkers

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)

Litte wy dizze controller iepenje en it bewurkje om in bytsje magy ta te foegjen nêstjsx/crud. Per klasse UsersController Litte wy sa'n dekorator tafoegje:

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

Crud is in decorator dy't foeget oan de controller de nedige metoaden foar it wurkjen mei it model. It model type wurdt oanjûn yn it fjild model.type decorator konfiguraasjes.
De twadde stap is om de ynterface út te fieren CrudController<User>. "Assembled" kontrôlerkoade sjocht der sa út:

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){}
}

En it is alles! No stipet de controller de heule set operaasjes mei it model! Leau my net? Litte wy ús applikaasje yn aksje besykje!

It meitsjen fan in Query Script yn TestMace

Om ús tsjinst te testen sille wy in IDE brûke om te wurkjen mei de API TestMace. Wêrom TestMace? Yn ferliking mei ferlykbere produkten hat it de folgjende foardielen:

• krêftige wurk mei fariabelen. Op it stuit binne der ferskate soarten fariabelen, dy't elk in spesifike rol spilet: ynboude fariabelen, dynamyske fariabelen, omjouwingsfariabelen. Eltse fariabele heart ta in knooppunt mei stipe foar it erfskip meganisme;
• Meitsje maklik skripts sûnder programmearring. Dit sil hjirûnder besprutsen wurde;
• in minsklik lêsber formaat wêrmei jo it projekt kinne bewarje yn ferzjekontrôlesystemen;
• autocompletion, syntaksis markearring, fariabele wearde markearring;
• API-beskriuwingsstipe mei de mooglikheid om te ymportearjen fan Swagger.

Litte wy ús server begjinne mei it kommando npm start en besykje tagong te krijen ta de list mei brûkers. De list mei brûkers, te beoardieljen troch ús controller-konfiguraasje, kin krigen wurde fan de url localhost:3000/users. Litte wy in fersyk meitsje oan dizze url.
Nei it útfieren fan TestMace kinne jo in ynterface lykas dit sjen:

Linksboppe is in projektbeam mei in woartelknooppunt Projekt. Litte wy besykje it earste fersyk oan te meitsjen om in list mei brûkers te krijen. Hjirfoar sille wy meitsje RequestStep node Dit wurdt dien yn it kontekstmenu fan it projektknooppunt Node tafoegje -> RequestStep.

Plak yn it URL-fjild localhost:3000/users en fier it fersyk út. Wy krije koade 200 mei in lege array yn it antwurd lichem. It is begryplik, wy hawwe noch gjinien tafoege.
Litte wy in skript meitsje dat de folgjende stappen sil befetsje:

1. it meitsjen fan in brûker;
2. fersyk foar de id fan 'e nij oanmakke brûker;
3. wiskje troch brûkers-id makke yn stap 1.

Dus, litte wy gean. Lit ús foar gemak in knooppunt meitsje lykas Folder. Yn essinsje is dit gewoan in map wêryn wy it heule skript sille bewarje. Om in mapknooppunt te meitsjen, selektearje Projekt út it kontekstmenu fan it knooppunt Node tafoegje -> Folder. Litte wy it knooppunt neame check-oanmeitsje. Binnen in knooppunt check-oanmeitsje Litte wy ús earste fersyk oanmeitsje om in brûker te meitsjen. Litte wy it nij oanmakke knooppunt neame meitsje-brûker. Dat is, op it stuit sil de nodehierarchy der sa útsjen:

Litte wy nei de iepen ljepper gean meitsje-brûker node. Litte wy de folgjende parameters ynfiere foar it fersyk:

• Fersyk type - POST
• URL - localhost:3000/brûkers
• Body - JSON mei wearde {"email": "[email protected]", "displayName": "New user", "username": "user"}

Lit ús folbringe dit fersyk. Us applikaasje seit dat it rekord is makke.

No, lit ús dit feit kontrolearje. Om te operearjen mei de id fan 'e oanmakke brûker yn folgjende stappen, moat dizze parameter bewarre wurde. It meganisme is perfekt foar dit. dynamyske fariabelen. Litte wy ús foarbyld brûke om te sjen hoe't jo mei har wurkje. Selektearje it item yn 'e parsed ljepper fan it antwurd, neist de id-knooppunt yn it kontekstmenu Tawize oan fariabele. Yn it dialoochfinster moatte jo de folgjende parameters ynstelle:

• node - yn hokker fan 'e foarâlden in dynamyske fariabele te meitsjen. Litte wy kieze check-oanmeitsje
• Variable name - de namme fan dizze fariabele. Lit ús skilje userId.

Hjir is hoe it proses fan it meitsjen fan in dynamyske fariabele derút sjocht:

No, elke kear as dizze query wurdt útfierd, sil de wearde fan 'e dynamyske fariabele wurde bywurke. En omdat dynamyske fariabelen stypje it meganisme fan hiërargyske erfskip, fariabele userId sil beskikber wêze yn neikommelingen check-oanmeitsje knooppunt fan elk nêstnivo.
Dizze fariabele sil nuttich wêze foar ús yn it folgjende fersyk. Wy sille nammentlik de nij oanmakke brûker freegje. As bern fan in knooppunt check-oanmeitsje wy sille meitsje in fersyk check-as bestiet mei parameter url lykweardich localhost:3000/users/${$dynamicVar.userId}. Besjoch ûntwerp ${variable_name} dit is it krijen fan de wearde fan in fariabele. Omdat Wy hawwe in dynamyske fariabele, dus om it te krijen moatte jo tagong krije ta it objekt $dynamicVar, dus folslein tagong ta in dynamyske fariabele userId sil der sa útsjen ${$dynamicVar.userId}. Litte wy it fersyk útfiere en soargje derfoar dat de gegevens goed oanfrege wurde.
De lêste stap oerbleaun is om ferwidering oan te freegjen. Wy hawwe it net allinich nedich om de wurking fan it wiskjen te kontrolearjen, mar ek, sa te sizzen, om ússels yn 'e databank op te romjen, om't De fjilden foar e-post en brûkersnamme binne unyk. Dat, yn 'e kontrôle-oanmeitsje-knooppunt sille wy in fersyk foar wiskjen fan brûkers meitsje mei de folgjende parameters

• Fersyk type - DELETE
• URL - localhost:3000/users/${$dynamicVar.userId}

Litte wy begjinne. Wy wachtsje. Wy genietsje fan it resultaat)

No, no kinne wy ​​dit hiele skript op elk momint útfiere. Om it skript út te fieren moatte jo selektearje út it kontekstmenu check-oanmeitsje node item run.

De knopen yn it skript sille ien nei de oare wurde útfierd
Jo kinne dit skript opslaan yn jo projekt troch te rinnen Triem -> Bewarje projekt.

konklúzje

Alle funksjes fan 'e brûkte ark koene gewoan net passe yn it formaat fan dit artikel. As foar de wichtichste skuldige - it pakket nêstjsx/crud - de folgjende ûnderwerpen bliuwe ûntdutsen:

• oanpaste falidaasje en transformaasje fan modellen;
• krêftige query-taal en it handige gebrûk oan 'e foarkant;
• opnij definiearje en tafoegjen fan nije metoaden oan crud controllers;
• swagger stipe;
• caching behear.

Sels wat yn it artikel beskreaun is is lykwols genôch om te begripen dat sels sa'n bedriuwskader as NestJS ark hat foar rappe tapassingsprototyping. En sa'n koele IDE lykas TestMace kinne jo te behâlden in opjûne tempo.

Boarnekoade foar dit artikel, tegearre mei it projekt TestMace, beskikber yn 'e repository https://github.com/TestMace/nest-rest. Om in projekt te iepenjen TestMace doch it gewoan yn 'e app Triem -> Projekt iepenje.

Boarne: www.habr.com