# Including in your project

EasyValidation has a number of artifacts and modules that you can add in your project.

1. **Core:** This module contains the main classes and all the built-in rules along with the views and collection kotlin extensions for validation purposes.

{% hint style="info" %}
Since these modules are under development, so these are not available for use yet.
{% endhint %}

1. **Toast:** This module contains all the views and collection kotlin extensions which displays `Toast` on invalid check.
2. **Snack:** This module contains all the views and collection kotlin extensions which displays `Snack` on invalid check.
3. **Error:** This module contains all the views and collection kotlin extensions which displays `Error` for views such as `EditText`, `TextInputLayout`, `AutoCompleteTextView` etc.
4. **Material Components:** This module contains the views and collection kotlin extensions for all the latest Material Components.

### Add library through jCenter and Gradle

&#x20;Add this in project's `build.gradle` file:

```groovy
// ...
allprojects {
    repositories {
        // ....
        mavenCentral()
    }
}
// ...
```

&#x20;And then add this in app's `build.gradle` file:

```groovy
def ev_version = "1.0.2" 

dependencies 
{ 
    // Core 
    implementation "com.wajahatkarim:easyvalidation-core:$ev_version" 
    
    // Shows Toasts by default for every validation error
    implementation "com.wajahatkarim:easyvalidation-toast:$ev_version"
}
```


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wajahatkarim.gitbook.io/easyvalidation/including-in-your-project.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
