Getting strange behaviour when running php artisan typescript:generate it appears it's trying to redeclare all the helpers which are auto loaded via composer.json's "autoload" { "files" : [ "app/helpers.php"] }

$ php artisan typescript:generate
PHP Fatal error:  Cannot redeclare selectedVesselId() (previously declared in C:\www\workrest\app\helpers.php:25) in C:\www\workrest\app\Core\helpers.php on line 23

   Symfony\Component\ErrorHandler\Error\FatalError 

  Cannot redeclare selectedVesselId() (previously declared in C:\www\workrest\app\Core\helpers.php:25)

This is only occurring when running typescript:generate, other CLI commands for artisan are working fine e.g.:

$ php artisan cache:clear
Application cache cleared!

Hi! What do you think about generation from Resources? e.g:

/**
 * @mixin \App\Models\Ticket
 */
class SupportResource extends JsonResource
{
    /**
     * Transform the resource into an array.
     *
     * @param \Illuminate\Http\Request $request
     * @return array
     */
    public function toArray($request): array
    {
        return [
            'id'         => $this->id,
            'title'      => $this->title,
            'message'    => $this->message,
            'created_at' => $this->created_at->diffForHumans(),
            'category'   => [
                'title' => $this->category->short_title,
                'hex_color'   => $this->category->hex_color,
            ],
            'status'     => [
                'title'     => $this->status->title,
                'hex_color' => $this->status->hex_color,
            ],
        ];
    }
}

It's possible? If it is, it will be a consistent interface in the backend and frontend.

• Add support for custom paths (to load relevant items from 'vendor' folder)
• Use explicit config values (with fallback) instead of spread operator in command
• Add the "generate" command to Generator Contract (since this is what's actually called from the TypeScriptGenerator class)
• Cleanup of generated code (additional white space, information message, etc)
• A generator for FormRequest classes
• TODO: Tests for request generator

Unfortunately this package does not work if the database has enum columns. DBAL does not support enum column types. In this PR the enum columns are mapped to strings, so we can still use the package when we have enum columns in our database. The TypeScript models will have a string type instead of an enum. Maybe not the best solution to this problem, but maybe it helps others for the time being.

By default, Laravel uses snake_case names for multi-word relations. The PR fixes that and adds an assertion. It also fixes composer.json loading that also works in a debugger environment or when tests is run not from project root (for example running using IDE)

Got the error during composer installation:

- Root composer.json requires based/laravel-typescript ^0.0.2 -> satisfiable by based/laravel-typescript[v0.0.2].
- based/laravel-typescript v0.0.2 requires illuminate/contracts ^8.37 -> found illuminate/contracts[v8.37.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another requ
ire.

Need support for illuminate/contracts v9

The classes that are generated are done using symfony's finder class, which can return files in any order returned by the filesystem.

This means that running the typescript:generate command can generate incredibly noisy diffs - whereas at least if it's sorted then the diffs should be slightly more sensible.

Hello seems awesome this package, I'm trying to use but i have this error:

If i remove the ripcord package still have differentes class with "Cannot declare class XXX, because the name is already in use

This project is great but there's a few lingering issues and it doesn't seem like there's any activity?

I see there's been some small commits like https://github.com/lepikhinb/laravel-typescript/commit/0ccde3251fdf09b0fb69055569a2fadc4230e052 but no commenting on issues/prs?

Make ModelGenerator filter out columns that have been hidden from the serialized representation of the Model (see: https://laravel.com/docs/9.x/eloquent-serialization#hiding-attributes-from-json).

The hidden attribute is commonly used with fields like password or remember_token.

Without filtering the types generated for a model misrepresent what is commonly sent by a server for this model:

{
  "id": 1,
  "name": "Test User",
  "email": "[email protected]",
  "email_verified_at": "2022-06-29T14:51:15.000000Z",
  "created_at": "2022-06-29T09:18:09.000000Z",
  "updated_at": "2022-06-29T09:18:09.000000Z"
}

for a generated type

export interface User {
    id: number;
    name: string;
    email: string;
    email_verified_at: string | null;
    created_at: string | null;
    updated_at: string | null;
}

instead of (without filtering hidden fields)

export interface User {
    id: number;
    name: string;
    email: string;
    password: string ;
    remember_token: string ;
    email_verified_at: string | null;
    created_at: string | null;
    updated_at: string | null;
}

https://github.com/lepikhinb/laravel-typescript/blob/5f2b2958d63c6b36bcd4e3ba44d711da7f49fcca/src/Generators/ModelGenerator.php#L225

Function isOneRelattion should be renamed to isOneRelation