Documentation
rte_2x
developPrimary versionrte_2xvuepress-migration
rte_2x
developPrimary versionrte_2xvuepress-migration
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  • Purpose
  • Steps
  • Outcome
  1. Coder devtools - CDT
  2. User guide

Validate sources

PreviousTesting Cubbles componentsNextCreate a demo webpackage

Last updated 5 years ago

Checking the quality of your code to find and fix errors is a common task. The offers the _validateSources task, which allows you to check the quality of the code of the artifacts of a webpackage. This task will check the following type of files within the :

  • Javascript files using and the .eslintrc config file located at the root folder of the active webpackage.

  • CSS files using and the .csslintrc config file located at the root folder of the CDT (normally it is called devtools).

  • JSON files using .

Purpose

To show how to validate the sources of the artifacts of the active webpackage using the _validateSources task.

Steps

You should run the task within the CDT folder (normally it is called devtools) as follows:

grunt _validateSources

Outcome

If errors are identified, they will be listed in the bash. Otherwise, a success message will be displayed.

CDT
active webpackage
eslint
csslint
jsonlint