Userfrosting best practice for helper functions -

what best practice have custom code (library of functions) in project using userfrosting?

as of now, modify existing userfrosting controllers, bloats nice concise code.

i guess there nice way keep custom functions in place, not interfere userfrosting's code , thereby not affected during userfrosting upgrades.

at moment, i'd have custom functions notifications, barcode etc.

guess using vendor folder under composer ideal? if so, how go it?

does userfrosting have extensibility symfony?

any / pointer appreciated!

thanks!

as of version 0.3.1, there no clean way separate core shipped code developer-implemented code. minor updates within version (so, hotfixes 0.3.1), best way keep up-to-date using git make project fork of userfrosting repository.

so example, might have spurgeon/brood-crm (your project repo) fork of userfrosting/userfrosting. can set userfrosting/userfrosting upstream remote repo. whenever hotfix released userfrosting/userfrosting, can sync fork upstream. pull changes main repo project, , give chance resolve merge conflicts (hopefully, there won't any).

for people not familiar distinction between git , github, should point out can of locally, without publishing fork on github.

userfrosting 4 (finally) have modular, extendable design. rather having directly modify shipped code, able override core routes, templates, schema, assets, etc in separate directory. upgrading version 0.3.x version 4, however, need done manually.