Replies: 2 comments 5 replies
-
|
I don't think all the changes are completed. @asanovr any idea what other changes are needed? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your fast answer. If we leave out the string id topic, how to handle the namespace topic in the stub classes when using custom classes? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
https://laravel-workflow.com/docs/configuration/publishing-config You can change the models that are used via the config file. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, i understood that - but various methods in |
Beta Was this translation helpful? Give feedback.
-
|
Ah it sounds like we might have to change something or create an interface. |
Beta Was this translation helpful? Give feedback.
-
|
Interface sounds like the perfect fit - probably needed for all customizable classes |
Beta Was this translation helpful? Give feedback.
-
|
@joni1993 I use string ids like this <?php
namespace App\Modules\Workflow\Models;
use Illuminate\Database\Eloquent\Concerns\HasUlids;
use Workflow\Models\StoredWorkflow as StoredWorkflowBase;
class StoredWorkflow extends StoredWorkflowBase
{
use HasUlids;
}
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
like three days ago i wanted to use strings for ids - i just found out thats possible with yesterdays release. 😃
But i am unsure how to implement it properly:
WorkflowStubwantsStoredWorkflowfromWorkflownamespace - if i create my ownStoredWorkflowmodel in App\Models thefromStoredWorkflowcall inWorkflowStubfails.I create the workflow manually like this:
If I don't create the Workflow manually like this
WorkflowStub::makeobviously fails because it usescreate()which fails without auto-incrementing integer key.May StoredWorkflow is the same as the supplied one but with these properties added:
Any help is appreciated :)
Beta Was this translation helpful? Give feedback.
All reactions