that's something we've discussed (adding a service provider in a capsule). At the moment there's no autoloading happening for that but you can of course register one in your capsule from your app config.php. there is a functionality to autoload an helper file in capsules, as well as a config file per capsule

yes helper I got! Yes I indeed can just do it like that, thanks a lot!

out of curiosity, what are you building using a capsule?

I am experimenting a bit for creating a base project to kickstart new sites. And I want to provide some minimalistic setup. I decided on Capsules to make them movable/extractable when needed in the future.

very cool. Share your previous sites with Twill in #811986244748705875 if you can!

Is there a repo I can contribute some documentation to? And yes once completed I will.

docs are in the Twill repo under /docs, it's a VuePress project

You can also feel free to put your doc ideas in a gist, which can then be added to the

awesome-twill

list

Great thank!

What is the best practice when you want to create a capsule with related things like Page and PageCategory ?

a capsule for each "module" ?

Models can coexist easily inside of a capsule but yes, 2 modules in 1 capsule require a bit of configuration. Mostly namespace stuff for the second or "child" module.

@User ok

@Rayderxx if the related module is only being used within the main model of the capsule, what @pboivin says

if not I think it makes sense to create another capsule

@User yeah but could be hard to handle with the database no ? if I have foreign key and indexes ...

Dependent capsules could be nice for this?

if (!Capsule::available('categories') { 
  throw new Exception('This capsule requires the categories capsule');
}

@User like you I have to build a starter kit for futur project , capsule sound the best way to do it ^^

This is not mine to announce but since we're talking about capsules, some very interesting things are happening @cwsdigital : https://github.com/cwsdigital This may be useful 🙂

@User didn't think about it but A categories capsule as a morph relation could do the trick

Hey, if there is a need to do some magic before edit form inputs get all values set, there is

getFormFields

function in the repository, right? But even if I set value to one specific input, it's not shown and the input shows -38 characters. Practically: model Product has attribute

stock

(which contains JSON) there is a formField named

stock

(which is a number) in

getFormFields

I set, e.g.,

$fields['stock'] = 22

and it does what I mentioned above. However if I set the

$object->stock = 22

, it works properly. Probably my understanding of what getFormFields does is limited or wrong, but all other fields get set as I declared in $fields array

Hey @User, this may be a bit naive but can't you rename your

stock

field to something else, like

stock_input

to avoid sharing the attribute name?

you are definitely right, I'm just trying to understand what goes on behind the scenes

Sure, that's great. I'm actually curious too, can you share your

getFormFields()

method?

here in #811986149064441927 or new thread?

Is it possible to create middleware (and register it) inside a capsule ?

You can (not sure if its the best approach): add a config.php that autoloads a bootstrap.php in the bootstrap.php add

App::register()

your capsule service provider, and do it from there (or just directly).

@User thx will try this