Hi I wanted to know the advantage of registering Asset Bundle following the process described in the docs like Process one in AppAsset.php
public $js = [
'js/myjsfile.js'
];
then in the view file adding Namespace like
namespace app\assets;
and then adding the use statement like
use app\assets\AppAsset;
AppAsset::register($this);
Instead of doing all this if I use Process Two
$this->registerJs('js/myjsfile.js', $this::POS_READY);
it works fine. So why should I use Process One.
- Any advantage and reason for this will be greatly appreciated.
- If I follow the process one Do I need to add all the js files in AppAsset.php individually.
Thanks.
Using Asset Bundles, you can also get the latest version from 'vendor' folder, so if you need to update some lib you don't need to manually do this since composer already do this.
One of the main reasons for using an Asset Bundle is that your assets' paths will always be correct. Consider:
will generate something like:
Which works great for non urlManager enabled urls, e.g.
http://localhost/yiiproject/index.php?r=user/update&id=8
because your browser looks for the js file at:/yiiproject/js/myjsfile.js
But if you enable urlManager, your url will look like
http://localhost/yiiproject/user/update/8
, which means your browser will look for your js file at:/yiiproject/user/update/8/js/myjsfile.js
.You could overcome this problem by using:
But the Asset Bundle basicly does that for you.
Asset Bundles have some advantages over normal registering. Apart from what @deacs said in his/her answer here are others:
All the features that makes bundles shine are found in docs