Gaur egun, REST APIa web aplikazioen garapenerako estandar bihurtu da, garapena zati independenteetan banatzeko aukera emanez. Gaur egun, Angular, React, Vue eta beste hainbat esparru ezagun erabiltzen dira UI-rako. Backend garatzaileek hainbat hizkuntza eta marko aukeratu ditzakete. Gaur bezalako esparru bati buruz hitz egin nahiko nuke NestJS. barruan gaude TestMace Barne proiektuetarako aktiboki erabiltzen dugu. Habia eta paketea erabiliz @nestjsx/crud, CRUD aplikazio sinple bat sortuko dugu.

Zergatik NestJS

Azkenaldian, JavaScript komunitatean backend esparru asko agertu dira. Eta funtzionalitateari dagokionez Nest-en antzeko gaitasunak ematen badituzte, gauza batean behin betiko irabaziko du: hau da arkitektura. NestJS-ren eginbide hauei esker, aplikazio industrialak sortzeko eta garapena talde handietara eska dezakezu:

• garapen-lengoaia nagusi gisa TypeScript erabiliz. NestJS JavaScript onartzen badu ere, baliteke funtzionalitate batzuk ez funtzionatzea, batez ere hirugarrenen paketeez ari bagara;
• DI edukiontzi baten presentzia, akoplatutako osagaiak sortzeko aukera ematen duena;
• Esparruaren funtzionaltasuna osagai trukagarri independenteetan banatzen da. Adibidez, kanpaiaren azpian marko gisa erabil daiteke expressEta azkartu, datu-basearekin lan egiteko, nest-ek loturak eskaintzen ditu tiporm, mangosta, sekuentziatu;
• NestJS plataforma agnostikoa da eta REST, GraphQL, Websockets, gRPC eta abar onartzen ditu.

Markoa bera Angular frontend esparruan inspiratuta dago eta kontzeptualki asko ditu berarekin.

NestJS instalatzea eta proiektua zabaltzea

Nest-ek pakete bat dauka habia/cli, oinarrizko aplikazio-esparru bat azkar zabaltzeko aukera ematen duena. Instala dezagun pakete hau globalki:

npm install --global @nest/cli

Instalatu ondoren, gure aplikazioaren oinarrizko markoa sortuko dugu izenarekin habia-rest. Hau komandoa erabiliz egiten da nest new nest-rest.

habia berri habia-atseden

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

Yarn aukeratuko dugu gure paketeen kudeatzaile gisa.
Une honetan zerbitzaria abi dezakezu komandoarekin npm start eta helbidera joatea http://localhost:3000 orrialde nagusia ikus dezakezu. Hala ere, ez da horregatik hemen bildu eta aurrera goaz.

Datu-basearekin lana konfiguratzea

PostrgreSQL aukeratu dut artikulu honetarako DBMS gisa. Ez dago gustuei buruzko eztabaidarik; nire ustez, hau da DBMS helduena, beharrezko gaitasun guztiak dituena. Esan bezala, Nest-ek hainbat paketerekin integratzen du datu-baseekin lan egiteko. Zeren Nire aukera PostgreSQL-en erori zenez, logikoa litzateke TypeORM ORM gisa aukeratzea. Instala ditzagun datu-basearekin integratzeko beharrezko paketeak:

yarn add typeorm @nestjs/typeorm pg

Ordenan, pakete bakoitza zertarako behar den:

1. typeorm - pakete bat zuzenean ORMtik bertatik;
2. @nestjs/typeorm - TypeORM paketea NestJS-rako. Proiektuaren moduluetan inportatzeko moduluak gehitzen ditu, baita dekoratzaile laguntzaileen multzo bat ere;
3. pg - PostgreSQL-rekin lan egiteko kontrolatzailea.

Ados, paketeak instalatuta daude, orain datu-basea bera abiarazi behar duzu. Datu-basea zabaltzeko, docker-compose.yml erabiliko dut eduki honekin:

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

Ikus dezakezunez, fitxategi honek 2 edukiontziren abiaraztea konfiguratzen du:

1. db datu-basea zuzenean duen edukiontzi bat da. Gure kasuan, postgresql 11.2 bertsioa erabiltzen da;
2. administratzailea: datu-baseen kudeatzailea. Datu-basea ikusteko eta kudeatzeko web interfaze bat eskaintzen du.

Tcp konexioekin lan egiteko, honako konfigurazio hau gehitu dut.

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

Hori da guztia, komandoarekin edukiontziak abiarazi ditzakezu docker-compose up -d. Edo komandoarekin aparteko kontsola batean docker-compose up.

Beraz, paketeak instalatu dira, datu-basea martxan jarri da, elkarren lagun egitea besterik ez da geratzen. Horretarako, fitxategi hau gehitu behar duzu proiektuaren errora: 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"
}
}

Konfigurazio hau cli typeorm-erako erabiliko da.

Ikus dezagun xehetasun gehiago konfigurazio hau. 3. eta 4. lerroetan ingurune-aldagaietatik erabiltzaile-izena eta pasahitza lortzen dugu. Hau komenigarria da hainbat ingurune dituzunean (dev, stage, prod, etab). Lehenespenez, erabiltzaile-izena postgres da eta pasahitza adibidea. Gainerako konfigurazioa hutsala da, beraz, parametro interesgarrienetan bakarrik zentratuko gara:

• synchronize - Aplikazioa abiaraztean datu-basearen eskema automatikoki sortu behar den adierazten du. Kontuz aukera honekin eta ez erabili produkzioan, bestela datuak galduko dituzu. Aukera hau erosoa da aplikazio bat garatzen eta arazketan. Aukera honen alternatiba gisa, komandoa erabil dezakezu schema:sync CLI TypeORM-tik.
• dropSchema - berrezarri eskema konexio bat ezartzen den bakoitzean. Aurrekoa bezala, aukera hau aplikazioaren garapenean eta arazketan soilik erabili behar da.
• entitateak - zein bide bilatu ereduen deskribapenak. Kontuan izan maskara bidezko bilaketak onartzen direla.
• cli.entitiesDir TypeORM CLI-tik sortutako ereduak lehenespenez gorde behar diren direktorioa da.

Gure Nest aplikazioan TypeORM-en eginbide guztiak erabili ahal izateko, modulua inportatu behar dugu. TypeOrmModule в AppModule. Horiek. zure AppModule itxura hau izango du:

aplikazioa.modulua.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 {}

Konturatuko zarenez, metodoa forRoot datu-basearekin lan egiteko konfigurazio bera transferitzen da ormconfig.ts fitxategian bezala

Azken ukitua geratzen da: gehitu hainbat zeregin TypeORM-ekin lan egiteko package.json-en. Kontua da CLI javascript-en idatzita dagoela eta nodejs ingurunean exekutatzen dela. Hala ere, gure eredu eta migrazio guztiak mekanografiaz idatziko dira. Horregatik, beharrezkoa da gure migrazioak eta ereduak transpilatzea CLIa erabili aurretik. Horretarako ts-node paketea behar dugu:

yarn add -D ts-node

Horren ondoren, gehitu beharrezko komandoak package.json-era:

"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"

Lehenengo komandoak, typeorm-ek, ts-node bilgarri bat gehitzen du TypeORM kli exekutatzeko. Gainerako komandoak, garatzaile gisa, ia egunero erabiliko dituzun lasterbide egokiak dira:
migration:generate — zure ereduen aldaketetan oinarritutako migrazioak sortzea.
migration:create — migrazio huts bat sortzea.
migration:run — Migrazioak martxan jartzea.
Beno, hori da orain, beharrezko paketeak gehitu ditugu, aplikazioa datu-basearekin funtzionatzeko konfiguratu dugu bai clitik eta baita aplikaziotik bertatik, eta DBMS ere abiarazi dugu. Gure aplikazioari logika gehitzeko garaia da.

CRUD sortzeko paketeak instalatzea

Nest soilik erabiliz, entitate bat sortu, irakurri, eguneratu eta ezabatzeko aukera ematen duen API bat sor dezakezu. Irtenbide hori ahalik eta malguena izango da, baina kasu batzuetan erredundantea izango da. Adibidez, prototipo bat azkar sortu behar baduzu, askotan malgutasuna sakrifikatu dezakezu garapenaren abiaduragatik. Esparru askok CRUD sortzeko funtzionaltasuna eskaintzen dute entitate jakin baten datu-eredua deskribatuz. Eta Nest ez da salbuespena! Funtzionalitate hau paketeak ematen du @nestjsx/crud. Bere gaitasunak oso interesgarriak dira:

• instalazio eta konfigurazio erraza;
• DBMS independentzia;
• Kontsulta-lengoaia indartsua iragazteko, orrialderatzeko, ordenatzeko, erlazioak eta habiaratutako entitateak, cachea, etab.
• frontend-ean eskaerak sortzeko paketea;
• kontrolagailu metodoak erraz gainditzea;
• konfigurazio txikia;
• swagger dokumentazio euskarria.

Funtzionalitatea hainbat paketetan banatzen da:

• @nestjsx/crud - Dekoratzaileak eskaintzen duen oinarrizko paketea Gordina() ibilbideak sortzeko, konfiguratzeko eta baliozkotzeko;
• @nestjsx/crud-request — frontend aldean erabiltzeko kontsulta-eraikitzailea/analizatzailea eskaintzen duen paketea;
• @nestjsx/crud-typeorm — TypeORM-ekin integratzeko pakete bat, oinarrizko TypeOrmCrudService zerbitzua datu-baseko entitateekin lan egiteko CRUD metodoekin eskaintzen duena.

Tutorial honetan paketeak beharko ditugu habiajsx/crud eta habiajsx/crud-typeorm. Lehenik eta behin, jar ditzagun

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

Paketeak klase-transformatzailea и klase-balidatzailea aplikazio honetan eredu-instantziak eraldatzeko eta sarrerako eskaerak baliozkotzeko arauen deklarazio deskribapena eskatzen da, hurrenez hurren. Pakete hauek egile berekoak dira, beraz, interfazeak antzekoak dira.

CRUDren zuzeneko ezarpena

Erabiltzaileen zerrenda bat hartuko dugu adibide eredu gisa. Erabiltzaileek eremu hauek izango dituzte: id, username, displayName, email. id - automatikoki gehitzeko eremua, email и username - eremu bereziak. Sinplea da! Gure ideia Nest aplikazio moduan inplementatzea besterik ez da geratzen.
Lehenik eta behin modulu bat sortu behar duzu users, erabiltzaileekin lan egiteaz arduratuko dena. Erabili dezagun NestJS-en cli-a eta exekutatu komandoa gure proiektuaren erro-direktorioan nest g module users.

habia g modulu erabiltzaileak

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)

Modulu honetan entitateen karpeta bat gehituko dugu, non modulu honen ereduak izango ditugun. Bereziki, gehi dezagun hemen user.entity.ts fitxategia erabiltzailearen ereduaren deskribapenarekin:

erabiltzaile.entitate.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;
}

Gure aplikazioak eredu hau “ikusteko” beharrezkoa da moduluan UsersModule inportatu TypeOrmModule honako eduki hau:

erabiltzaileak.modulua.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 {}

Hau da, hemen inportatzen dugu TypeOrmModule, non metodo parametro gisa forFeature Modulu honekin lotutako ereduen zerrenda adierazten dugu.

Datu-basean dagokion entitatea sortzea besterik ez da geratzen. Migrazio mekanismoak helburu horietarako balio du. Modeloen aldaketetan oinarritutako migrazio bat sortzeko, komandoa exekutatu behar duzu npm run migration:generate -- CreateUserTable:

spoiler izenburua

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

Ez genuen migrazioa eskuz idatzi beharrik izan, dena magiaz gertatu zen. Hau ez al da miraria! Hala ere, hori ez da guztia. Ikus dezagun sortutako migrazio fitxategia:

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

Ikus dezakezunez, migrazioa abiarazteko metodoa ez ezik, atzera botatzeko metodoa ere sortu zen automatikoki. Zoragarria!
Migrazio hori zabaltzea besterik ez da geratzen. Hau komando honekin egiten da:

npm run migration:run.

Hori da, orain eskema-aldaketak datu-basera migratu dira.
Jarraian, erabiltzaileekin lan egiteaz arduratuko den zerbitzu bat sortuko dugu eta oinordetzan hartuko dugu TypeOrmCrudService. Intereseko entitatearen biltegia eraikitzaile nagusiaren parametrora pasatu behar da, gure kasuan User biltegia.

erabiltzaileak.zerbitzua.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);
}
}

Zerbitzu hau kontrolagailuan beharko dugu users. Kontrolagailu bat sortzeko, idatzi kontsolan nest g controller users/controllers/users

habia g kontroladore erabiltzaile/kontrolatzaile/erabiltzaile

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)

Ireki dezagun kontrolagailu hau eta editatu magia pixka bat gehitzeko habiajsx/crud. Klase bakoitzeko UsersController Gehitu dezagun honelako dekoratzaile bat:

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

Gordina kontroladoreari modeloarekin lan egiteko beharrezko metodoak gehitzen dizkion dekoratzailea da. Eredu mota eremuan adierazten da model.type dekoratzaileen konfigurazioak.
Bigarren urratsa interfazea ezartzea da CrudController<User>. "Muntatua" kontroladorearen kodea honelakoa da:

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

Eta dena! Orain kontrolagailuak eragiketa multzo osoa onartzen du modeloarekin! Ez didazu sinesten? Proba dezagun gure aplikazioa ekintzan!

TestMace-n kontsulta-script bat sortzea

Gure zerbitzua probatzeko IDE bat erabiliko dugu APIarekin lan egiteko TestMace. Zergatik TestMace? Antzeko produktuekin alderatuta, abantaila hauek ditu:

• aldagaiekin lan indartsua. Momentuz, hainbat aldagai mota daude, eta bakoitzak eginkizun zehatz bat betetzen du: aldagai barneratuak, aldagai dinamikoak, inguruneko aldagaiak. Aldagai bakoitza herentzia mekanismorako euskarria duen nodo bati dagokio;
• Sortu erraz scriptak programatu gabe. Jarraian eztabaidatuko da hori;
• gizakiek irakurtzeko moduko formatu bat, proiektua bertsio-kontrol sistemetan gordetzeko aukera ematen duena;
• osaketa automatikoa, sintaxia nabarmentzea, balio aldakorra nabarmentzea;
• API deskribapen laguntza Swagger-etik inportatzeko aukerarekin.

Hasi dezagun gure zerbitzaria komandoarekin npm start eta saiatu erabiltzaileen zerrendara sartzen. Erabiltzaileen zerrenda, gure kontroladorearen konfigurazioaren arabera, localhost:3000/users url-etik lor daiteke. Egin dezagun eskaera url honetara.
TestMace exekutatu ondoren honelako interfaze bat ikus dezakezu:

Goiko ezkerrean erro-nodo bat duen proiektuaren zuhaitza dago Proiektua. Saia gaitezen lehen eskaera sortzen erabiltzaileen zerrenda lortzeko. Horretarako sortuko dugu Eskatu Urratsera nodoa Proiektua nodoaren testuinguru-menuan egiten da Gehitu nodoa -> RequestStep.

URL eremuan, itsatsi localhost:3000/users eta exekutatu eskaera. 200 kodea jasoko dugu erantzunaren gorputzean matrize huts batekin. Ulergarria da, oraindik ez dugu inor gehitu.
Sortu dezagun urrats hauek izango dituen script bat:

1. erabiltzaile bat sortzea;
2. Erabiltzaile sortu berriaren id-a eskatzea;
3. 1. urratsean sortutako erabiltzaile IDaren bidez ezabatuz.

Beraz, goazen. Erosotasunerako, sor dezagun antzeko nodo bat Folder. Funtsean, script osoa gordeko dugun karpeta bat besterik ez da. Karpeta-nodo bat sortzeko, hautatu Proiektua nodoaren laster-menuan Gehitu nodoa -> Karpeta. Dei diezaiogun nodoari egiaztatu-sortu. Nodo baten barruan egiaztatu-sortu Sor dezagun gure lehen eskaera erabiltzaile bat sortzeko. Dei diezaiogun sortu berri den nodoari sortu-erabiltzailea. Hau da, une honetan nodoen hierarkia itxura hau izango du:

Goazen irekitako fitxara sortu-erabiltzailea nodoa. Sar ditzagun eskaerarako parametro hauek:

• Eskaera mota - POST
• URL - localhost: 3000/users
• Gorputza - JSON balioarekin {"email": "[email protected]", "displayName": "New user", "username": "user"}

Bete dezagun eskaera hau. Gure aplikazioak erregistroa sortu dela dio.

Beno, egiazta dezagun datu hau. Sortutako erabiltzailearen idarekin hurrengo urratsetan funtzionatzeko, parametro hau gorde behar da. Mekanismoa ezin hobea da horretarako. aldagai dinamikoak. Erabili gure adibidea haiekin nola lan egin aztertzeko. Erantzunaren analizatutako fitxan, testuinguru-menuko id nodoaren ondoan, hautatu elementua Esleitu aldagaiari. Elkarrizketa-koadroan parametro hauek ezarri behar dituzu:

• Nodoa — arbasoetako zeinetan aldagai dinamiko bat sortu. Aukera dezagun egiaztatu-sortu
• Aldagaiaren izena — aldagai honen izena. Deitu dezagun userId.

Hona hemen aldagai dinamiko bat sortzeko prozesua nolakoa den:

Orain, kontsulta hau exekutatzen den bakoitzean, aldagai dinamikoaren balioa eguneratuko da. Eta zeren aldagai dinamikoek herentzia hierarkikoaren mekanismoa onartzen dute, aldagai userId ondorengoetan egongo da eskuragarri egiaztatu-sortu edozein habia-mailako nodoa.
Aldagai hau hurrengo eskaeran erabilgarria izango zaigu. Alegia, sortu berri den erabiltzaileari eskatuko diogu. Nodo baten seme-alaba bezala egiaztatu-sortu eskaera bat sortuko dugu existitzen den egiaztatu parametroarekin url berdina localhost:3000/users/${$dynamicVar.userId}. Ikusi diseinua ${variable_name} hau aldagai baten balioa lortzea da. Zeren Aldagai dinamiko bat dugu, beraz, lortzeko objektura sartu behar duzu $dynamicVar, hau da, aldagai dinamiko batean guztiz sartzea userId itxura hau izango du ${$dynamicVar.userId}. Exekutatu dezagun eskaera eta ziurtatu datuak behar bezala eskatzen direla.
Azken urratsa ezabatzea eskatzea da. Ezabaketaren funtzionamendua egiaztatzeko ez ezik, nolabait esateko, datu-basean geure burua garbitzeko ere behar dugu, izan ere. Posta elektronikoa eta erabiltzaile-izenaren eremuak bakarrak dira. Beraz, check-create nodoan ezabatzeko erabiltzaile eskaera bat sortuko dugu parametro hauekin

• Eskaera mota - DELETE
• URL - localhost:3000/users/${$dynamicVar.userId}

Abiarazi gaitezen. Itxaroten dugu. Emaitza gozatzen dugu)

Beno, orain edozein unetan exekutatu dezakegu script osoa. Scripta exekutatzeko laster-menuan hautatu behar duzu egiaztatu-sortu nodoaren elementua Korrika egin.

Script-eko nodoak bata bestearen atzetik exekutatuko dira
Script hau zure proiektuan gorde dezakezu exekutatuz Fitxategia -> Gorde proiektua.

Ondorioa

Erabilitako tresnen ezaugarri guztiak ezin izan dira artikulu honen formatuan sartu. Errudun nagusiari dagokionez - paketea habiajsx/crud - gai hauek agerian geratzen dira:

• ereduen baliozkotze pertsonalizatua eta eraldaketa;
• kontsulta-lengoaia indartsua eta erabilera erosoa aurrealdean;
• crud kontrolagailuei metodo berriak birdefinitzea eta gehitzea;
• swagger laguntza;
• cachearen kudeaketa.

Hala ere, artikuluan deskribatzen dena ere nahikoa da ulertzeko NestJS bezalako enpresa-esparru batek ere aplikazioen prototipo azkarra egiteko tresnak dituela. Eta halako IDE polita bezalakoa TestMace erritmo jakin bati eusteko aukera ematen du.

Artikulu honen iturburu kodea, proiektuarekin batera TestMace, biltegian eskuragarri https://github.com/TestMace/nest-rest. Proiektu bat irekitzeko TestMace besterik gabe egin aplikazioan Fitxategia -> Ireki proiektua.

Iturria: www.habr.com