🏷️component:tag

Commands Definition and Purpose

What does it do?

The Drimz Editor allows browsing the components according to the ID and the version we provide while "tagging" the component using the CLI.

Tagging will happen automatically after adding so you can skip to the component: push page

After adding the component we tag it to start using it by designers in our team. We use "Tag"

How to run?

The syntax is as follows:

drimz component:tag local/<component name> <component_version>

For example, tagging a component named "AboutHero" with version 1.0.0

drimz component:tag local/AboutHero 1.0.0

Note that the arguments are crucial for the command to run. The name will be the reference for you

Did it work?

We will usually run status to see that the operation was successful (see )

However, you do get a message (in our case we tagged a component named AboutHero)

Running drimz status will show:

Notice that the component has the version we provided and the status is now "staged".

IMPORTANT:

Drimz runs some compilations on the component to "learn" about the component. In the tagging process, there may be some output if any library or code does send some logs during compile time, you should only care about the last 2 lines of the logging process.