A tool for automatically generating typescript/javascript objects and utilities based on their PHP counterparts.
Laravel Version | Paragon Version |
---|---|
11.0 | 1.0.x |
10.0 | 1.0.x |
composer require kirschbaum-development/paragon
TL;DR: Run the following command to generate Typescript (or Javascript) enums from your PHP enums:
php artisan paragon:enum:generate
That's it. Now, wherever you may have had enums in your project, "paragons" or near perfect duplicates of those have been recreated inside of resources/js/enums
. Here are some examples of the API:
use App\Enums\Status;
Status::Active;
Status::Active->value;
Status::cases();
Status::from('active');
Status::tryFrom('active');
import Status from '@/js/enums/Status.ts';
Status.Active;
Status.Active.value;
Status.cases();
Status.from('active');
Status.tryFrom('active');
As you can see the API is nearly the same, the only difference being how the two languages expect you to access objects!
Generating javascript enums
This package also supports generating Javascript enums. To do so, simply pass the --javascript
flag to the command:
php artisan paragon:enum:generate --javascript
A good majority of the time it is useful to use public methods to return a proper human-readable label or some other functionality on an enum. Paragon got this covered too. Assuming the following method exists on the above Status
enum:
public function label(): string
{
return match ($this) {
self::Active => 'Active',
self::Inactive => 'Inactive',
};
}
public function color(): string
{
return match ($this) {
self::Active => 'bg-green-100',
self::Inactive => 'bg-red-100',
};
}
The following method would become accessible using TypeScript:
Status.Active.label() // 'Active'
Status.Inactive.label() // 'Inactive'
Status.Active.color() // 'bg-green-100'
Status.Inactive.color() // 'bg-red-100'
While this package ignores static methods on the PHP Enums, we allow you to create additional methods that Paragon will make available for every generated Enum.
php artisan paragon:enum:add-method
This will create a new file at resources/js/vendors/paragon/enums
containing a method. You are free to do whatever you need inside this file. You have direct access to this.items
which allows you to interact with the enum cases in whatever way you need. Just keep in mind that because the items are "frozen", you can't mutate them directly. An example would be to have a method that automatically generates a select list from your Enum.
There may be enums or enum methods that you don't want inside your automatically generated code. If this is the case simply use the IgnoreParagon
attribute.
use Kirschbaum\Paragon\Concerns\IgnoreParagon;
#[IgnoreParagon]
enum IgnoreMe
{
case Ignored;
}
use Kirschbaum\Paragon\Concerns\IgnoreParagon;
enum Status
{
...
#[IgnoreParagon]
public method ignoreMe()
{
...
}
}
You can publish the configuration file by running php artisan vendor:publish
and locating the Paragon config which will be published at config/paragon.php
.
It is recommended that the generated path for the enums is added to the .gitignore
file. Make sure to run this command during deployment if you do this.
Install the vite-plugin-watch
plugin in your project via npm
:
npm i -D vite-plugin-watch
In your vite.config.js
file, import the plugin, and add the plugin paramaters to your plugins array:
import { watch } from "vite-plugin-watch";
export default defineConfig({
plugins: [
// ...
watch({
pattern: "app/Enums/**/*.php",
command: "php artisan paragon:generate-enums",
}),
],
});
Enums are a fantastic addition to the PHP-verse but are really lame in the TypeScript-verse. However, it can be annoying trying to get those enum values on the front-end of your project. Are you supposed to pass them as a method when returning a view or perhaps via an API? This generator solves that problem by scraping your app directory for any and all enums and recreates them as TypeScript classes so you can import them directly into your Vue, React, or Svelte front-end!
Let's take a closer look at a simple PHP enum and its generated Typescript code.
namespace App\Enums;
enum Status: string
{
case Active = 'active';
case Inactive = 'inactive';
}
import Enum from '../Enum.ts';
type StatusDefinition = {
name: string;
value: string;
};
class Status extends Enum {
protected static items = Object.freeze({
Active: Object.freeze({
name: 'Active',
value: 'active',
}),
Inactive: Object.freeze({
name: 'Inactive',
value: 'inactive',
}),
});
public static get Active(): AlarmStatusDefinition {
return this.items['Active'];
}
public static get Inactive(): AlarmStatusDefinition {
return this.items['Inactive'];
}
}
export default Status;
At first glance it appears as though a lot more stuff is happening, but the above generated code allows us to interact
with the enum in a nearly identical way as in PHP. And you may notice the generated TypeScript class extends the Enum
class. This gives us some underlying functionality that is available to every enum.