Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why not embed instanceOf as an extension built into ZendTwig #5

Closed
celtic34fr opened this issue Apr 2, 2017 · 2 comments
Closed

Why not embed instanceOf as an extension built into ZendTwig #5

celtic34fr opened this issue Apr 2, 2017 · 2 comments
Assignees

Comments

@celtic34fr
Copy link

Hi,
I use Twig in my personal project GraphicObjectTemplating (ZF2/ZF3).
Giving access to TWIG under ZF2 / ZF3 is interesting, but having an adaptation of the basic templates would be more useful, as your extension instanceOf.
If this can help you, I would have both extensions and basic templates to offer you

  • layout/layout, error/index, error/404, application/index/index (templates),
  • intanceOf, typeOf (test extensions),
  • getclass, gettype, arrayexception (for error/index template), checkBoolean, substr, strpos, instring (function extensions),
  • contains (subchain is in string), update (update of table by key / value), unset (deletion occurance in array by key) (filter extension)

If you are interested, I can send you the ZF3 sources by email at your request, not all in my project on github (celti34fr / graphic-object-templating)

I found in the TWIG repository a tag refused by Fabien POTENCIER: switch/case that I adapted, I can also provide you.

Gilbert ARMENGAUD
celtic34fr
gilbert.armengaud@gmail.com
(Béziers - Hérault - Occitanie - France)

@OxCom
Copy link
Owner

OxCom commented Apr 2, 2017

Hello,

Good idea, I will think about that, I'll provide You my decision in a week.

Thank You!

@OxCom OxCom self-assigned this Apr 2, 2017
@OxCom
Copy link
Owner

OxCom commented Apr 10, 2017

I decided that this extensions for Twig should be created as separate packages, because all extensions will require more dependencies, that is not applicable.

So, it should be done as separate project per extension.

@OxCom OxCom closed this as completed Apr 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants