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
  • The npm module version
  1. Coder devtools - CDT
  2. User guide

Rename an artifact

PreviousGenerate a README fileNextConfigure network proxy

Last updated 5 years ago

To rename an artifact, you need to rename folders, files and refactor some code. The offers the _webpackage-renameArtifact task to perform that process automatically.

Purpose

To describe how to rename an artifact using the _webpackage-renameArtifact task.

Steps

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

grunt  _webpackage-renameArtifact

Second, a list of available artifacts will be displayed. You should choose the one to be renamed. Type the number of the artifact in the displayed list, then press Enter.

Outcome

The task will perform the following changes according to the type of artifact:

Changes

Elementary

Compound

Utility

App

Refactor manifest

X

X

X

X

Rename associated folder

X

X

X

X

Refactor generated docs

X

X

Refactor generated demo

X

X

Refactor associated resources

X

X

Refactor associated template

X

X

Refactor associated js file

X

Rename template, logic and style files

X

The npm module version

You can use an npm module that serves the same purposes called . The module can be used from the command line or in a node script.

CDT
cubx-rename-artifact