[VOLT] Support for embedding blocks into other blocks

[applejohnny]

With inheritance of multiple files like a.volt extends b.volt extends c.volt, I have to use embedding blocks. Otherwise there's no profit to use inheritance more than one nesting level.

[xpundel]

The same question. Is there a plans to implement this feature?

[xpundel]

Greetings!
Is there any plans to implement this feature?

[breezewish]

Hi, is there any plans? I think this feature is important.

[gianks]

+1

[gsouf]

I upvote for the feature

[Raistlfiren]

Agreed. It would be nice to have a block inside an if statement.

[kvokov]

I think it's very useful feature. Waiting for this!

[gsouf]

Actually this is why i'm using twig instead of volt

[raisoblast]

+1 for this great feature

[vladimmi]

Any improvements after almost a year? As for me, this is the most needed missing feature in Volt

[phalcon]

This will be implemented in Phalcon 2 with Zephir

[redstrike]

At this moment, Phalcon 2 is missing some features from 1.x and still not stable enough for using in production. Why don't you fix this bug in Phalcon 1.3.3?

[immortalx]

+1 to implement this feature in 1.3.x

[vladimmi]

It seems, developers are focused only on 2.x branch and will not implement any new features in 1.3. Anyway, this wasn't implemented for 1.5 years so... You can use Twig if you need this feature.

[gsouf]

@phalcon told

This will be implemented in Phalcon 2 with Zephir

[manish-ga]

Just curious, when will Phalcon 2 be released?

[datanator]

So the reason not to use Twig or Smarty is that I suppose Volt is considerably faster in compiling templates since I suppose that the engine is written in C. And it seems that the compiled code is pretty clean too...
However, template inheritance screams for nested blocks... you can hardly live without these.
Plus One for nested blocks (and verbatim and block-plugins)

[gsouf]

And i use twig because I assume that the template are cached once they are parsed ;)

[michanismus]

+1 We need it so bad!

[redstrike]

I have moved to Twig completely for rendering templates. It's more mature and has better docs.

[AGvin]

Hi guys, do we have some updates for this feature?

[reedgz]

phalcon commented on Jan 14, 2014
This will be implemented in Phalcon 2 with Zephir

Any news on this one? Definitely needed.

I am developing current project with volt, just ran into the problem. Now I have to decide if I want to re-write all views in twig/smarty. Only two weeks from the deadline now.

[andresgutierrez]

@reedgz I'll be addressing this soon

[reedgz]

@andresgutierrez Thanks man. I am still developing with volt; just used some include to work around the problem. Fortunately my views are relatively simple.

[ilyavaiser]

Nothing at all?

[michanismus]

I switched to Twig as well...

[redstrike]

I wonder why Phalcon team created VOLT, which causes a lot of troubles for framework users. Twig's mature and performance are too great (templates are compiled to php, then it will be cached by Zend Opcache + add-on Twig C extension).

What happens if Phalcon team drops Volt to improve project's development speed?

[andresgutierrez]

@redstrike "A LOT OF TROUBLES" "TOO GREAT"

[alejandrovasta]

I need this feature as soon as possible! please, it's a shame that this magnificent framework doesn't have something so important. Thanks

[valVk]

up

[hdjvieira]

+1

[krazzer]

This is the only reason I use Twig instead of Volt. Fixing this would be awesome, I would switch back to Volt right away.

[valVk]

One of the most commented feature in this milestone and in the same time in the end of TODO list )

[4ctarus]

+1

[victorhramos]

Im giving up using Volt cause that feature, in large and complex templates is very painful maintain using only one level of inheritance. Using phalcon only in API for Vue front.

[datanator]

I would suggest to reads jurijags reply again. Use either Twig or Smarty3 in stead of Volt, it might be slower in compilation time (when the template changes) but it won't matter in execution time (when the template is rendered).
I dismissed many of Phalcons features, but still use the framework basis since it is a fast and clean one.

[Jurigag]

No twig or smarty3, only blade - twig and smarty3 are not really plain php - for each blocks etc they steal are using many objects and classes for no reason. Blade is pretty much similar in speed as volt on cached views.

[datanator]

Don't know Blade too well but does it support infinite inheritance? From the examples I only see one level, similar to Volt. I agree with Jurigag that Smarty and to a lesser extent Twig is somewhat bloated, but one might like the modular and extensible nature of that. In the end the compiled template defines most of its speed and efficiency. It boils down to a matter of taste. We can agree that Volt still has to improve to compete...

[ug-code]

+1
it's very useful feature.
actually "Laravel blade" is more useful than "volt"
see also => "yield, section"

[erickmajor]

@niden

In version 4.0 of Phalcon it will be possible to use blocks {% block %} under conditions {% if %} and {% else %}?

[niden]

Closing in favor of phalcon/cphalcon#13855. Will revisit if the community votes for it, or in later versions.

[gianks]

Is there a deadline for this feature or will it be postponed forever?

[niden]

This will be addressed when we start working on v6 which will be the PHP version of Phalcon. There is no deadline as of yet and it has not been abandoned. Once v5 is out and stable we will start working on v6

[gianks]

What do you mean by PHP version? Is Phalcon Zephir extension going to be dropped? If that's the case, how will Phalcon retain its advantage over other frameworks without a natively compiled leg? I get that a pure PHP version allows Phalcon to be used wherever you can run PHP but what really makes Phalcon desirable are its performance. I'm afraid it might just become another Symfony over time but I hope to be wrong! Il mer 22 set 2021, 15:53 Nikolaos Dimopoulos ***@***.***> ha scritto:

…

This will be addressed when we start working on v6 which will be the PHP version of Phalcon. There is no deadline as of yet and it has not been abandoned. Once v5 is out and stable we will start working on v6 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/phalcon/cphalcon/issues/329#issuecomment-924953482>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXFM2HC44MUHXU33O3O2D3UDHNVXANCNFSM4AC4UPQQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[niden]

This has all been outlined in our blog (https://blog.phalcon.io).

• v5 is the extension. It will remain as such.
• v6 will be rewritten in PHP. Additionally benchmarks will be created for this version to identify slow areas of the code. Those areas will be also written in Zephir and will be offered as an extension. So you can install Phalcon with composer but if you want additional boost, you can also install the extension for v6.

[Jeckerson]

@gianks Please read this blog post - https://blog.phalcon.io/post/phalcon-roadmap

[vladimmi]

Stale bots are the plague of GitHub making any inactivity a sign of "everything is great now" and closing unresolved issues...

[niden]

Stale bots are the plague of GitHub making any inactivity a sign of "everything is great now" and closing unresolved issues...

Yeah, after today I am considering deactivating it. I had to remove the stale label from over 20 issues so far :/