Filmanet Resources stuck in Queue as Idle

TiagoSilvaPereira / vemto2-issues

Repository to track Vemto 2 Issues

5 stars 0 forks source link

Filmanet Resources stuck in Queue as Idle #150

Closed adampatterson closed 5 months ago

adampatterson commented 5 months ago

I was playing around with the app trying to assess it's capabilities and so far really like it.

I tried to add some simple Filament resources but they are all stuck as Idle.

TiagoSilvaPereira commented 5 months ago

@adampatterson the Filament resources stuck as Idle if you don't install Filament in the project (Vemto shows a modal asking you to install Filament before generating the code). It is necessary because Vemto needs to boot the whole Laravel application, and if it generates Filament classes without Filament being installed, Laravel will not boot correctly and Vemto may not work

adampatterson commented 5 months ago

Humm, I created a new project and chose filament then. It did install Filament 3.2

I do have a Filament AdminPanelProvider, but that's all I noticed.

I also tried creating some CRUD pages and they didn't generate anything.

TiagoSilvaPereira commented 5 months ago

@adampatterson is this still on Idle state?

adampatterson commented 5 months ago

@TiagoSilvaPereira yea it's been a day.

TiagoSilvaPereira commented 5 months ago

@adampatterson, could you please record a video showing the entire process? I did not manage to reproduce this issue, so if you could provide more information, this would help a lot

adampatterson commented 5 months ago

Hello @TiagoSilvaPereira sure I can try to do that tonight, it's been a busy week :)

I am on the trial and it's probably got a few days left.

adampatterson commented 5 months ago

@TiagoSilvaPereira I recreated the project and feel silly.

1) I didn't know to click the play button, I sort of assumed it was to run unit tests.

It doesn't help that I named the project Test 2) when I do it's telling me that it can't generate files on a trial but
it says I have more than 15 tables but I only have 11

https://d.pr/v/7KFVWG

TiagoSilvaPereira commented 5 months ago

Hi @adampatterson it accounts for all tables on your project, including the Laravel default tables (which you can see under the "Laravel" schema section). Could you please try with a smaller project where you can finish code generation and check if this work?

adampatterson commented 5 months ago

@TiagoSilvaPereira sute thing, I'll check my tables. I included users but I assume migration and jobs will also count so that could be what put me over.

TiagoSilvaPereira commented 5 months ago

@adampatterson, that's perfect! Yes, it does account for all application tables, including the 8 tables generated by Laravel migrations. I want to change this behavior in the future, but I haven't had time yet. Best regards!

adampatterson commented 5 months ago

I reduced the number of tables but my previous issue is causing problems.

I haven't change anything but always have a schema changes so the queues are still idle.

https://github.com/TiagoSilvaPereira/vemto2-issues/issues/149

TiagoSilvaPereira commented 5 months ago

@adampatterson closing as it seems to be resolved. Please feel free to reopen if necessary