![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@webiny/api-admin-settings
Advanced tools
npm install --save @webiny/api-headless-cms
Or if you prefer yarn:
yarn add @webiny/api-headless-cms
Due to possibility of multiple storage operations, the tests are completely decoupled from those storage operations.
The jest.setup.js is using @webiny/project-utils/testing/presets.js to find and load all the packages containing @webiny/api-headless-cms
and storage-operations
keywords in their package.json
file.
Those packages are then used to build the test run - one for each of the packages. So depending on how many storage operations there are in the repository, that much of api-headless-cms
tests will run.
To make it possible for api-headless-cms tests to run with a storage operations package you MUST create presets.js
file in storage-operations-package-path/__tests__/__api__/
directory. That file is loaded when setting up the api-headless-cms tests.
It MUST contain the testEnvironment
variable which contains path to the environment definition file.
That environment file MUST define the test environment which extends NodeEnvironment
class.
Test environment MUST expose __getStorageOperationsPlugins
method, via this.global
property of the class, which will load the required plugins in the api-headless-cms
tests.
The first implementation of the decoupled storage operations is DynamoDB/Elasticsearch, which you can find in @webiny/api-headless-cms-ddb-es. Files which you can check to help you define your own presets and test environment are:
__getStorageOperationsPlugins
to the testsFor the WebStorm (PhpStorm,...) when starting a test you must have some values defined in the run/debug configurations screen:
--inspect=9229
PATH_TO_YOUR_PROJECT_ROOT
example:
~/webiny/webiny-js/
For DynamoDB + Elasticsearch storage operations tests:
--keyword=cms:base --keyword=cms:ddb-es
For the DynamoDB storage operations tests:
--keyword=cms:base --keyword=cms:ddb
Note that base keyword is the cms:base
. It tells Jest setup to load the api-headless-cms
tests with the api-headless-cms-ddb-es tests.
If you want to use local Elasticsearch:
ELASTICSEARCH_PORT=9200;LOCAL_ELASTICSEARCH=true
Nothing if you do not want to use the local Elasticsearch.
FAQs
Admin settings getter
We found that @webiny/api-admin-settings demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.