conformance-rules-editor

by cdisc-org TypeScript Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | conformance-rules-editor Summary

conformance-rules-editor is a TypeScript library. conformance-rules-editor has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

conformance-rules-editor

Support

Quality

Security

License

Reuse

Support

conformance-rules-editor has a low active ecosystem.

It has 5 star(s) with 1 fork(s). There are 6 watchers for this library.

It had no major release in the last 6 months.

There are 38 open issues and 59 have been closed. On average issues are closed in 99 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of conformance-rules-editor is current.

Quality

conformance-rules-editor has no bugs reported.

Security

conformance-rules-editor has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

conformance-rules-editor is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

conformance-rules-editor releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of conformance-rules-editor

Get all kandi verified functions for this library.

conformance-rules-editor Key Features

No Key Features are available at this moment for conformance-rules-editor.

conformance-rules-editor Examples and Code Snippets

No Code Snippets are available at this moment for conformance-rules-editor.

Community Discussions

No Community Discussions are available at this moment for conformance-rules-editor.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install conformance-rules-editor

Install Node.js version 16: https://nodejs.org/en/download/releases.
Install frontend dependencies - From the root directory, run the command: npm install. Install api dependencies - From the ./api directory, run the command: npm install.
Install frontend dependencies - From the root directory, run the command: npm install
Install api dependencies - From the ./api directory, run the command: npm install
Install static web app node libraries by running the following commands: npm install -g @azure/static-web-apps-cli
Using VSCODE, install the "Azure Functions" extension.
Create a local.settings.json in the API folder to support local development of the API. It should contain the following values which provide information for the staticwebapp config and the Microsoft Graph API for Users' name resolution: { "IsEncrypted": false, "Values": { "EXECUTE_RULE_URL": "<RULE_EXECUTOR_URL>", "FUNCTIONS_WORKER_RUNTIME": "node", "SWA_TENANT_ID": "<Static Web App Tenant ID>", "SWA_CLIENT_ID": "<Static Web App Client ID>", "SWA_CLIENT_SECRET": "<Static Web App Client Secret>", "CORE_AUTHOR_GROUP": "<User Group ID for write permissions>", "RULE_SCHEMA_URL": "https://raw.githubusercontent.com/cdisc-org/cdisc-rules-engine/main/resources/schema/CORE-base.json" } }
Storage - There is a base Storage abstraction which allows for any storage implementation. Currently there are 2 storage implementations. Using one of these implementations requires the additional env variables to be added to the local.settings.json file CosmosDB (SQL) Tell the editor which storage implementation to use: "STORAGE_PROVIDER": "CosmosSQL", "COSMOS_BASE_URL": <COSMOS_BASE_URL>, "COSMOS_KEY": <COSMOS_KEY>, "COSMOS_DATABASE": <COSMOS DB Name>, "COSMOS_CONTAINER": <COSMOS Container Name>, Optional env variable to ignore unauthorized https connections when cosmosdb is running in a local emulator: "NODE_TLS_REJECT_UNAUTHORIZED": "0", Drupal Tell the editor which storage implementation to use: "STORAGE_PROVIDER": "Drupal", "DRUPAL_BASE_URL": "<DRUPAL_API_URL>", "DRUPAL_CLIENT_ID": "<DRUPAL_API_CLIENT_ID>", "DRUPAL_CLIENT_SECRET": "<DRUPAL_API_CLIENT_SECRET>", "DRUPAL_GRANT_TYPE": "<DRUPAL_API_GRANT_TYPE>", "DRUPAL_PATH": "<DRUPAL_API_PATH>", "DRUPAL_SCOPE": "<DRUPAL_API_SCOPE>",

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: