Due to the large code refactoring in version 6, what changes need to be made in the customization for the transition?
Version 6 changes, refactoring question
Collapse
X
-
I think it might be bit too early to tell. From another thread there was promised of "backward compatibility as best as we can" so I don't think anything will break but who know.
Best to follow this section: https://github.com/espocrm/espocrm/issues/1743
EspoCRM – Open Source CRM Application. Contribute to espocrm/espocrm development by creating an account on GitHub.
Currently only these two is "planned" (don't know what it mean though:
- Less coupling
- Utilizing new DI
-
There is a lot of changes in API of classes. In most cases manual customizations will be backward compatible. There will be beta version for 6.0 where you will be able to test your customizations.
Unfortunately, I'm not able to document all changes, it would be very hard for me. In the future we are going to have a backend API documentation, so it will be easier to track changes.If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.Comment
-
Hello,
i have see many commit by Yuri about : Di ... what's is Di ?
in belgium, di.be it's a store who sell many thinks for women or homeIf you could give the project a star on GitHub. EspoCrm believe our work truly deserves more recognition. Thanks.Comment
-
"Direct Input" maybe? Sound enough like a coding term. -
It's for Dependency injection =) https://github.com/espocrm/documenta...elopment/di.md
-
-
Comment
Comment