0
Fork 0
mirror of https://github.com/verdaccio/verdaccio.git synced 2025-01-20 22:52:46 -05:00
verdaccio/test/unit/partials/config/yaml
Juan Picado c91d6beb8b
feat: add rate limit to web endpoints (#2799)
* feat: add rate limit to web endpoints

* fix: types express conflict

* fix: undefined issue

* fix: tests
2021-12-23 17:35:31 +01:00
..
api-jwt
api.spec
notify
profile feat: add rate limit to web endpoints (#2799) 2021-12-23 17:35:31 +01:00
security
server
api.search.spec.yaml feat: implement search v1 endpoint (#2256) 2021-05-15 16:39:03 +02:00
api.spec.yaml feat: add rate limit to web endpoints (#2799) 2021-12-23 17:35:31 +01:00
api.web.spec.yaml feat: add rate limit to web endpoints (#2799) 2021-12-23 17:35:31 +01:00
default.yaml feat: add rate limit to web endpoints (#2799) 2021-12-23 17:35:31 +01:00
deprecated-pkgs-basic.yaml
pkg.access.spec.yaml
pkgs-basic-no-access.yaml
pkgs-basic-no-proxy.yaml
pkgs-basic-no-publish.yaml
pkgs-basic.yaml
pkgs-custom.yaml
pkgs-empty.yaml
pkgs-multi-group.yaml
pkgs-nosuper-wildcard-custom.yaml
README.md chore: fix eslint warnings (#1471) 2019-09-26 18:22:14 +02:00
store.spec.yaml
token.spec.yaml chore: fix eslint warnings (#1471) 2019-09-26 18:22:14 +02:00
uplink-basic.yaml
uplink-wrong.yaml

Yaml Configurations

This folder host all sort of configurations for testing. We use yaml instead json configuration files for different reasons, maintenability, avoid polute with non use data and contributors can easily understand them.

The files on this folder should be small as possible, there is a custom config file for all tests (default.yaml) and the following configuration aims to override those part are need it for the test.

Contribute

  • Each topic ideally should have his own folder if many scenarios might be part of the test. eg: profile, security
    • Include different scenarios inside of the folder with enough context to indenty the use case.
  • Foder or file, should be named as the test that used them. eg: api.spec.yaml -> api.spec.ts
  • Don't use the same config file in multiple test, it increase maintenance complexity.
  • Try to include only the props are require for the test:
  • Comment the config files, don't be shy, add as much context you think is need it for future contributors.

Note: Some configurations might be not aligned with this rules, but in the future all files should be follow them for consistency.