# Config

you can publish a config file by using this command

```
php artisan vendor:publish --tag="tomato-category-config"
```

you can publish views file by using this command

```
php artisan vendor:publish --tag="tomato-category-views"
```

you can publish languages file by using this command

```
php artisan vendor:publish --tag="tomato-category-lang"
```

you can publish migrations file by using this command

```
php artisan vendor:publish --tag="tomato-category-migrations"
```

## Config File

```php
<?php

return [
    /*
     * Types For
     * 
     * you may need a types for accounts and another for content
     */
    "for" => [
        "accounts"=> [
            "ar" => "الحسابات",
            "en" => "Accounts"
        ],
        "content"=> [
            "ar" => "المحتوي",
            "en" => "Content"
        ]
    ],
    
    /*
     * Types Of Type
     * 
     * it's a sub-type of type like account type or content type
     */
    "types" => [
        "type"=> [
            "ar" => "النوع",
            "en" => "Type"
        ],
        "status"=> [
            "ar" => "الحالة",
            "en" => "Status"
        ],
    ],
    
    
    /*
     * Features
     */
    "features" => [
        "category" => false,
        "types" => true
    ],
    
    /*
     * Category Middleware
     * 
     * you can add a middleware to the category APIs routes
     */
    "middleware" => [],
    
    /*
     * Category Resource
     * 
     * you can custom API resource for categories
     */
    "categories_resource" => null,
    
    /*
     * Types Resource
     * 
     * you can custom API resource for types
     */
    "types_resource" => null,
];

```


---

# 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://docs.tomatophp.com/plugins/tomato-category/config.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.