> For the complete documentation index, see [llms.txt](https://atomico.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomico.gitbook.io/doc/api/props/value-cycle-as-prop.md).

# Value cycle as prop

Atomico has a really efficient and simple type validation method, the type validation works in the following way:

![](https://3886616710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-L_3P325_k_Bez-RbDQb-887967055%2Fuploads%2F4EFXJd6HEnqI3uS4EHAf%2Fprop-en.png?alt=media\&token=c0931022-6c5b-4135-9cec-cccf9b873699)

### **Cycle as attribute**:

the given value is transformed to the corresponding type, be it String, Number, Boolean, Array or Object, once transformed it is sent to the [**cycle as property**](#cycle-as-a-property).

### Cycle as property:

evaluates if the value is of the declared type:

* **If it corresponds to the type:**
  1. It is saved in props.
  2. An event is emitted (if this has been configured in the prop).
  3. It is reflected as an attribute (if this has been configured in the prop).
  4. It is sent to the update queue and subsequent rendering.
* **It does not correspond to the type**: an error is created by console with the following data:
  * **target**: Instance of the webcomponent.
  * **value**: Input value.
  * **type**: expected type.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atomico.gitbook.io/doc/api/props/value-cycle-as-prop.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.