Hozirgi vaqtda REST API veb-ilovalarni ishlab chiqish uchun standart bo'lib, rivojlanishni mustaqil qismlarga bo'lish imkonini beradi. Hozirda UI uchun Angular, React, Vue va boshqalar kabi turli mashhur ramkalar qo'llaniladi. Backend dasturchilari turli xil tillar va ramkalardan tanlashlari mumkin. Bugun men bunday ramka haqida gapirmoqchiman . Biz kirdik Biz undan ichki loyihalar uchun faol foydalanamiz. Nest va paketdan foydalanish , biz oddiy CRUD ilovasini yaratamiz.
Nima uchun NestJS
So'nggi paytlarda JavaScript hamjamiyatida juda ko'p backend ramkalar paydo bo'ldi. Va agar funksionallik nuqtai nazaridan ular Nest-ga o'xshash imkoniyatlarni taqdim qilsalar, u bir narsada albatta g'alaba qozonadi - bu arxitektura. Quyidagi NestJS xususiyatlari sanoat ilovalarini yaratish va yirik jamoalar uchun ishlab chiqishni kengaytirish imkonini beradi:
- Asosiy dastur tili sifatida TypeScript dan foydalanish. NestJS JavaScript-ni qo'llab-quvvatlasa-da, ba'zi funksiyalar ishlamasligi mumkin, ayniqsa, agar biz uchinchi tomon paketlari haqida gapiradigan bo'lsak;
- erkin bog'langan komponentlarni yaratishga imkon beruvchi DI konteynerining mavjudligi;
- Ramkaning funksionalligi mustaqil almashtiriladigan komponentlarga bo'linadi. Masalan, kaput ostida uni ramka sifatida ishlatish mumkin , va , ma'lumotlar bazasi bilan ishlash uchun, Nest out of box bog'lashlarni ta'minlaydi , , ;
- NestJS agnostik platforma hisoblanadi va REST, GraphQL, Websockets, gRPC va boshqalarni qo'llab-quvvatlaydi.
Ramkaning o'zi Angular frontend ramkasidan ilhomlangan va kontseptual jihatdan u bilan juda ko'p umumiyliklarga ega.
NestJS-ni o'rnatish va loyihani o'rnatish
Nest paketni o'z ichiga oladi /cli, bu sizga asosiy dastur ramkasini tezda joylashtirish imkonini beradi. Keling, ushbu paketni global miqyosda o'rnatamiz:
npm install --global @nest/cliO'rnatishdan so'ng biz nom bilan ilovamizning asosiy ramkasini yaratamiz nest-rest. Bu buyruq yordamida amalga oshiriladi nest new nest-rest.
yangi nest-rest
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/nestPaket menejerimiz sifatida ipni tanlaymiz.
Ushbu nuqtada siz serverni buyruq bilan boshlashingiz mumkin npm start va manzilga borish asosiy sahifani ko'rishingiz mumkin. Biroq, biz bu erga to'planganimiz uchun emas va biz davom etamiz.
Ma'lumotlar bazasi bilan ishlashni sozlash
Men ushbu maqola uchun DBMS sifatida PostrgreSQL ni tanladim. Ta'mlar haqida hech qanday bahs yo'q, menimcha, bu barcha kerakli imkoniyatlarga ega bo'lgan eng etuk DBMS. Yuqorida aytib o'tilganidek, Nest ma'lumotlar bazalari bilan ishlash uchun turli paketlar bilan integratsiyani ta'minlaydi. Chunki Mening tanlovim PostgreSQL-ga to'g'ri kelganligi sababli, TypeORM-ni ORM sifatida tanlash mantiqan to'g'ri bo'lar edi. Keling, ma'lumotlar bazasi bilan integratsiya qilish uchun kerakli paketlarni o'rnatamiz:
yarn add typeorm @nestjs/typeorm pg
Har bir paket nima uchun kerak bo'lsa:
- typeorm - to'g'ridan-to'g'ri ORMning o'zidan to'plam;
- @nestjs/typeorm - NestJS uchun TypeORM to'plami. Loyiha modullariga import qilish uchun modullar, shuningdek yordamchi dekoratorlar to'plamini qo'shadi;
- pg - PostgreSQL bilan ishlash uchun haydovchi.
OK, paketlar o'rnatildi, endi siz ma'lumotlar bazasini o'zi ishga tushirishingiz kerak. Ma'lumotlar bazasini joylashtirish uchun men quyidagi tarkib bilan docker-compose.yml dan foydalanaman:
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:8080Ko'rib turganingizdek, ushbu fayl 2 ta konteynerni ishga tushirishni sozlaydi:
- db to'g'ridan-to'g'ri ma'lumotlar bazasini o'z ichiga olgan konteynerdir. Bizning holatlarimizda postgresql 11.2 versiyasi ishlatiladi;
- adminer - ma'lumotlar bazasi menejeri. Ma'lumotlar bazasini ko'rish va boshqarish uchun veb-interfeysni taqdim etadi.
Tcp ulanishlari bilan ishlash uchun men quyidagi konfiguratsiyani qo'shdim.
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 hereHammasi shu, siz konteynerlarni buyruq bilan boshlashingiz mumkin docker-compose up -d. Yoki buyruq bilan alohida konsolda docker-compose up.
Shunday qilib, paketlar o'rnatildi, ma'lumotlar bazasi ishga tushirildi, qolgan narsa ularni bir-biri bilan do'stlashdir. Buning uchun loyiha ildiziga quyidagi faylni qo'shishingiz kerak: 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"
}
}
Ushbu konfiguratsiya cli typeorm uchun ishlatiladi.
Keling, ushbu konfiguratsiyani batafsil ko'rib chiqaylik. 3 va 4-qatorlarda biz muhit o'zgaruvchilaridan foydalanuvchi nomi va parolni olamiz. Agar sizda bir nechta muhit mavjud bo'lsa (dev, sahna, prod va boshqalar) bu qulay. Odatiy bo'lib, foydalanuvchi nomi postgres va parol misoldir. Konfiguratsiyaning qolgan qismi ahamiyatsiz, shuning uchun biz faqat eng qiziqarli parametrlarga e'tibor qaratamiz:
- sinxronlash - Ilova ishga tushganda ma'lumotlar bazasi sxemasi avtomatik ravishda yaratilishi kerakligini ko'rsatadi. Ushbu parametr bilan ehtiyot bo'ling va uni ishlab chiqarishda ishlatmang, aks holda siz ma'lumotlarni yo'qotasiz. Ushbu parametr dasturni ishlab chiqish va disk raskadrovka qilishda qulaydir. Ushbu parametrga alternativa sifatida siz buyruqdan foydalanishingiz mumkin
schema:syncCLI TypeORM dan. - dropSchema - har safar ulanish o'rnatilganda sxemani qayta o'rnatish. Oldingi variant kabi, ushbu parametr faqat dasturni ishlab chiqish va tuzatish paytida ishlatilishi kerak.
- ob'ektlar - modellarning tavsiflarini izlash uchun qaysi yo'llar. Niqob bo'yicha qidiruv qo'llab-quvvatlanishini unutmang.
- cli.entitiesDir - TypeORM CLI-dan yaratilgan modellar sukut bo'yicha saqlanishi kerak bo'lgan katalog.
Nest ilovamizda TypeORM ning barcha xususiyatlaridan foydalanishimiz uchun modulni import qilishimiz kerak. TypeOrmModule в AppModule. Bular. sizning AppModule quyidagicha ko'rinadi:
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 {}Siz sezganingizdek, usul forRoot ma'lumotlar bazasi bilan ishlash uchun bir xil konfiguratsiya ormconfig.ts faylidagi kabi uzatiladi
Yakuniy teginish qoladi - package.json da TypeORM bilan ishlash uchun bir nechta vazifalarni qo'shing. Gap shundaki, CLI javascriptda yozilgan va nodejs muhitida ishlaydi. Biroq, bizning barcha modellarimiz va migratsiyalarimiz shriftda yoziladi. Shuning uchun, CLI dan foydalanishdan oldin migratsiyalarimiz va modellarimizni transpilyatsiya qilish kerak. Buning uchun bizga ts-tugun paketi kerak:
yarn add -D ts-node
Shundan so'ng, package.json ga kerakli buyruqlarni qo'shing:
"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"Birinchi buyruq, typeorm, TypeORM cli-ni ishga tushirish uchun ts-tugun o'ramini qo'shadi. Qolgan buyruqlar dasturchi sifatida deyarli har kuni foydalanadigan qulay yorliqlardir:
migration:generate — modellaringizdagi oʻzgarishlar asosida migratsiya yaratish.
migration:create — boʻsh migratsiyani yaratish.
migration:run - migratsiyani boshlash.
Xo'sh, endi biz kerakli paketlarni qo'shdik, dasturni cli-dan ham, dasturning o'zidan ham ma'lumotlar bazasi bilan ishlash uchun sozladik, shuningdek, DBMSni ishga tushirdik. Ilovamizga mantiq qo'shish vaqti keldi.
CRUD yaratish uchun paketlarni o'rnatish
Faqat Nest’dan foydalanib, ob’ektni yaratish, o‘qish, yangilash va o‘chirish imkonini beruvchi API yaratishingiz mumkin. Ushbu yechim imkon qadar moslashuvchan bo'ladi, lekin ba'zi hollarda u ortiqcha bo'ladi. Misol uchun, agar siz tezda prototip yaratishingiz kerak bo'lsa, tez-tez rivojlanish tezligi uchun moslashuvchanlikni qurbon qilishingiz mumkin. Ko'pgina ramkalar ma'lum bir ob'ektning ma'lumotlar modelini tavsiflash orqali CRUD yaratish uchun funksionallikni ta'minlaydi. Nest ham bundan mustasno emas! Ushbu funksiya paket tomonidan taqdim etiladi . Uning imkoniyatlari juda qiziq:
- oson o'rnatish va sozlash;
- DBMS mustaqilligi;
- filtrlash, sahifalash, saralash, aloqalar va ichki ob'ektlarni yuklash, keshlash va h.k. qobiliyatiga ega kuchli so'rovlar tili;
- front-endda so'rovlarni yaratish uchun paket;
- boshqaruvchi usullarini oson bekor qilish;
- kichik konfiguratsiya;
- Swagger hujjatlarini qo'llab-quvvatlash.
Funktsionallik bir nechta paketlarga bo'lingan:
- - dekorativ taqdim etadigan asosiy paket () marshrutni yaratish, sozlash va tekshirish uchun;
- — frontend tomonida foydalanish uchun so'rovlar yaratuvchisi/parserini ta'minlovchi paket;
- — TypeORM bilan integratsiya uchun to'plam, asosiy TypeOrmCrudService xizmatini ma'lumotlar bazasidagi ob'ektlar bilan ishlash uchun CRUD usullari bilan ta'minlaydi.
Ushbu qo'llanmada bizga paketlar kerak bo'ladi jsx/crud va jsx/crud-typeorm. Birinchidan, ularni qo'yaylik
yarn add @nestjsx/crud class-transformer class-validatorPaketlar и ushbu ilovada mos ravishda model namunalarini o'zgartirish va kiruvchi so'rovlarni tasdiqlash qoidalarining deklarativ tavsifi talab qilinadi. Ushbu paketlar bir xil muallifdan, shuning uchun interfeyslar o'xshash.
CRUD ni bevosita amalga oshirish
Biz namuna sifatida foydalanuvchilar ro'yxatini olamiz. Foydalanuvchilar quyidagi maydonlarga ega bo'ladi: id, username, displayName, email. id - maydonni avtomatik oshirish, email и username - noyob maydonlar. Hammasi oddiy! Faqat bizning fikrimizni Nest ilovasi shaklida amalga oshirish qoladi.
Avval siz modul yaratishingiz kerak users, foydalanuvchilar bilan ishlash uchun kim javobgar bo'ladi. Keling, NestJS dan cli dan foydalanamiz va loyihamizning asosiy katalogidagi buyruqni bajaramiz nest g module users.
nest g moduli foydalanuvchilari
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)Ushbu modulda biz ob'ektlar papkasini qo'shamiz, unda biz ushbu modulning modellariga ega bo'lamiz. Xususan, bu yerga foydalanuvchi modeli tavsifi bilan user.entity.ts faylini qo'shamiz:
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;
}Ushbu model bizning ilovamiz tomonidan "ko'rinishi" uchun modulda kerak UsersModule Import TypeOrmModule quyidagi tarkib:
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 {}Ya'ni, bu erda biz import qilamiz TypeOrmModule, bu erda usul parametri sifatida forFeature Biz ushbu modulga tegishli modellar ro'yxatini ko'rsatamiz.
Ma'lumotlar bazasida tegishli ob'ektni yaratish qoladi. Migratsiya mexanizmi ana shu maqsadlarga xizmat qiladi. Modellardagi o'zgarishlar asosida migratsiya yaratish uchun siz buyruqni bajarishingiz kerak npm run migration:generate -- CreateUserTable:
Spoiler sarlavhasi
$ npm run migration:generate -- CreateUserTable
Migration /home/dmitrii/projects/nest-rest/migrations/1563346135367-CreateUserTable.ts has been generated successfully.
Done in 1.96s.Migratsiyani qo'lda yozishimiz shart emas edi, hamma narsa sehrli tarzda sodir bo'ldi. Bu mo''jiza emasmi! Biroq, bu hammasi emas. Keling, yaratilgan migratsiya faylini ko'rib chiqaylik:
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"`);
}
}Ko'rib turganingizdek, nafaqat migratsiyani boshlash usuli, balki uni orqaga qaytarish usuli ham yaratilgan. Ajoyib!
Qolgan narsa bu migratsiyani yo'lga qo'yishdir. Bu quyidagi buyruq bilan amalga oshiriladi:
npm run migration:run.Hammasi shu, endi sxema o'zgarishlari ma'lumotlar bazasiga ko'chirildi.
Keyinchalik, biz foydalanuvchilar bilan ishlash uchun javobgar bo'ladigan va uni meros qilib oladigan xizmatni yaratamiz TypeOrmCrudService. Qiziqarli ob'ektning ombori asosiy konstruktor parametriga o'tkazilishi kerak, bizning holatlarimizda User ombori.
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);
}
}Bizga kontrollerda ushbu xizmat kerak bo'ladi users. Tekshirish moslamasini yaratish uchun konsolga kiriting nest g controller users/controllers/users
nest g kontroller foydalanuvchilari/kontrollerlari/foydalanuvchilari
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)Keling, ushbu kontrollerni ochamiz va biroz sehr qo'shish uchun uni tahrirlaymiz jsx/crud. Har bir sinf uchun UsersController Keling, shunday dekoratorni qo'shamiz:
@Crud({
model: {
type: User
}
}) model bilan ishlash uchun kerakli usullarni boshqaruvchiga qo'shadigan dekorativ. Model turi maydonda ko'rsatilgan model.type dekorativ konfiguratsiyalar.
Ikkinchi qadam - interfeysni amalga oshirish CrudController<User>. "Yig'ilgan" boshqaruvchi kodi quyidagicha ko'rinadi:
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){}
}Va bu hammasi! Endi kontroller model bilan barcha operatsiyalar to'plamini qo'llab-quvvatlaydi! Menga ishonmaysizmi? Keling, ilovamizni amalda sinab ko'raylik!
TestMace-da so'rov skriptini yaratish
Xizmatimizni sinab ko'rish uchun API bilan ishlash uchun IDE dan foydalanamiz . Nima uchun TestMace? Shu kabi mahsulotlar bilan taqqoslaganda, u quyidagi afzalliklarga ega:
- o'zgaruvchilar bilan kuchli ish. Hozirgi vaqtda o'zgaruvchilarning bir nechta turlari mavjud bo'lib, ularning har biri o'ziga xos rol o'ynaydi: o'rnatilgan o'zgaruvchilar, dinamik o'zgaruvchilar, muhit o'zgaruvchilari. Har bir o'zgaruvchi meros mexanizmini qo'llab-quvvatlaydigan tugunga tegishli;
- Dasturlashsiz osongina skriptlarni yarating. Bu quyida muhokama qilinadi;
- loyihani versiyalarni boshqarish tizimlarida saqlashga imkon beruvchi inson tomonidan o'qiladigan format;
- avtoto'ldirish, sintaksisni ajratib ko'rsatish, o'zgaruvchan qiymatni ajratib ko'rsatish;
- Swagger-dan import qilish imkoniyati bilan API tavsifini qo'llab-quvvatlash.
Serverimizni buyruq bilan boshlaylik npm start va foydalanuvchilar ro'yxatiga kirishga harakat qiling. Bizning kontroller konfiguratsiyasiga ko'ra foydalanuvchilar ro'yxatini localhost:3000/users URL manzilidan olish mumkin. Keling, ushbu URL manziliga so'rov yuboraylik.
TestMace-ni ishga tushirgandan so'ng siz quyidagi kabi interfeysni ko'rishingiz mumkin:
Yuqori chap tomonda ildiz tuguniga ega loyiha daraxti joylashgan . Keling, foydalanuvchilar ro'yxatini olish uchun birinchi so'rovni yaratishga harakat qilaylik. Buning uchun biz yaratamiz tugun Bu loyiha tugunining kontekst menyusida amalga oshiriladi Tugun qo'shing -> RequestStep.
URL maydoniga localhost:3000/users ni qo'ying va so'rovni bajaring. Javob tanasida bo'sh massiv bilan 200 kodini olamiz. Bu tushunarli, biz hali hech kimni qo'shganimiz yo'q.
Keling, quyidagi bosqichlarni o'z ichiga olgan skript yarataylik:
- foydalanuvchi yaratish;
- yangi yaratilgan foydalanuvchining identifikatorini so'rash;
- 1-bosqichda yaratilgan foydalanuvchi identifikatori tomonidan o'chirish.
Xo'sh, ketaylik. Qulaylik uchun shunga o'xshash tugun yarataylik . Aslida, bu biz butun skriptni saqlaydigan papka. Papka tugunini yaratish uchun tugunning kontekst menyusidan Project ni tanlang Tugun qo'shish -> Jild. Keling, tugunni chaqiraylik tekshirish-yaratish. Tugun ichida tekshirish-yaratish Keling, foydalanuvchi yaratish uchun birinchi so'rovimizni yarataylik. Keling, yangi yaratilgan tugunni chaqiraylik yaratish-foydalanuvchi. Ya'ni, hozirda tugun ierarxiyasi quyidagicha ko'rinadi:
Keling, ochiq tabga o'tamiz yaratish-foydalanuvchi tugun. So'rov uchun quyidagi parametrlarni kiritamiz:
- So'rov turi - POST
- URL - localhost: 3000/foydalanuvchilar
- Tana - qiymatga ega JSON
{"email": "[email protected]", "displayName": "New user", "username": "user"}
Keling, bu iltimosni bajaraylik. Bizning ilovamiz yozuv yaratilganligini aytadi.
Xo'sh, keling, bu haqiqatni tekshirib ko'raylik. Keyingi bosqichlarda yaratilgan foydalanuvchi identifikatori bilan ishlash uchun ushbu parametr saqlanishi kerak. Buning uchun mexanizm juda mos keladi. . Keling, ular bilan qanday ishlashni ko'rib chiqish uchun misolimizdan foydalanamiz. Javobning tahlil qilingan yorlig'ida, kontekst menyusidagi id tugunining yonidagi elementni tanlang O'zgaruvchiga tayinlash. Muloqot oynasida siz quyidagi parametrlarni o'rnatishingiz kerak:
- Node — ajdodlarning qaysi birida dinamik o'zgaruvchini yaratish. Keling, tanlaymiz tekshirish-yaratish
- Argumentlar nomi - bu o'zgaruvchining nomi. Qo'ng'iroq qilaylik
userId.
Dinamik o'zgaruvchini yaratish jarayoni quyidagicha ko'rinadi:
Endi, har safar bu so'rov bajarilganda, dinamik o'zgaruvchining qiymati yangilanadi. Va chunki dinamik o'zgaruvchilar ierarxik meros mexanizmini qo'llab-quvvatlaydi, o'zgaruvchan userId avlodlarida mavjud bo'ladi tekshirish-yaratish har qanday joylashtirish darajasidagi tugun.
Bu o'zgaruvchi keyingi so'rovda biz uchun foydali bo'ladi. Ya'ni, biz yangi yaratilgan foydalanuvchini so'raymiz. Bir tugunning bolasi sifatida tekshirish-yaratish so'rov yaratamiz mavjudligini tekshirish parametr bilan url teng localhost:3000/users/${$dynamicVar.userId}. Dizaynni ko'rish ${variable_name} bu o'zgaruvchining qiymatini oladi. Chunki Bizda dinamik o'zgaruvchi bor, shuning uchun uni olish uchun ob'ektga kirishingiz kerak $dynamicVar, ya'ni dinamik o'zgaruvchiga to'liq kirish userId shunday ko'rinadi ${$dynamicVar.userId}. Keling, so'rovni bajaramiz va ma'lumotlar to'g'ri so'ralganligiga ishonch hosil qilamiz.
Qolgan oxirgi qadam - o'chirishni so'rash. Bizga nafaqat o'chirish jarayonini tekshirish, balki ma'lumotlar bazasida o'zimizni tozalash uchun ham kerak, chunki Elektron pochta va foydalanuvchi nomi maydonlari noyobdir. Shunday qilib, check-create tugunida biz quyidagi parametrlar bilan foydalanuvchini o'chirish so'rovini yaratamiz
- So'rov turi - O'chirish
- URL -
localhost:3000/users/${$dynamicVar.userId}
Keling, ishga tushiramiz. kutamiz. Biz natijadan mamnunmiz)
Endi biz ushbu skriptni istalgan vaqtda ishga tushirishimiz mumkin. Skriptni ishga tushirish uchun siz kontekst menyusidan tanlashingiz kerak tekshirish-yaratish tugun elementi yugurish.
Skriptdagi tugunlar birin-ketin bajariladi
Ushbu skriptni ishga tushirish orqali loyihangizga saqlashingiz mumkin Fayl -> Loyihani saqlash.
xulosa
Amaldagi vositalarning barcha xususiyatlari oddiygina ushbu maqola formatiga mos kelmadi. Asosiy aybdor - paketga kelsak jsx/crud - quyidagi mavzular ochilmagan:
- modellarni maxsus tekshirish va o'zgartirish;
- kuchli so'rovlar tili va undan old tomondan qulay foydalanish;
- xomashyo kontrollerlariga yangi usullarni qayta belgilash va qo'shish;
- shafqatsiz qo'llab-quvvatlash;
- keshlash boshqaruvi.
Biroq, hatto NestJS kabi korporativ tizimda ham tez dastur prototipini yaratish vositalari mavjudligini tushunish uchun maqolada tasvirlangan narsalar ham etarli. Va shunga o'xshash ajoyib IDE berilgan sur'atni saqlab qolish imkonini beradi.
Loyiha bilan birga ushbu maqola uchun manba kodi , omborda mavjud . Loyihani ochish uchun buni faqat ilovada qiling Fayl -> Loyihani ochish.
Manba: www.habr.com