niclasvaneyk / blade-devtools Goto Github PK

1. Dom/Forwarded Stuff: Everything not in @props / constructor that was forwarded to the root HTML tag
2. AlpineJS: x-* attributes that are also
3. The rest. This is the interesting part I suppose, where Models and rich PHP classes will be rendered

• Component Tags
• Props

Similar to how Vue and Reacts devtools, or even the elements panel does this

Hi, I'm very interested with this extension and I hope it will be released someday !

I saw this package spatie/laravel-blade-comments and maybe you can use it for the "comments around components" part.

Since the serialization of data properties can become quite huge, we should hash serialized objects and de-duplicate them before including them in the final output.

Imagine Filament, where every table row contains a model instance, which gets quite large really fast. I think this is required in order to achieve #4

• Compiled View file
• View file
• Component class (if existing)
• Leverage IGNITION_LOCAL_SITE_PATH and IGNITION_REMOTE_SITE_PATH variables. Also DEBUGBAR_EDITOR and IGNITION_EDITOR.

If https://github.com/filamentphp/demo can be analyzed in the devtools and does not break, I think its fairly safe to release a beta / 0.1 release

Livewire does not like the IDs we include as comments, since there must only be one top-level element. However, Livewire has their own ID mechanism, that looks very similar to ours. Maybe this can be leveraged somehow.

• don't break Livewire components
• highlight Livewire components in devtools
• somehow handle Livewire updates