Best Practice / Resources for Blade

blade
sage9

#61

I was thinking about that, too. The “Roots way” as shown in functions.php would appear to be an array. So for consistency that makes sense.


#62

Does anyone know if it’s possible to extract an array in Blade templates?

In PHP 7, I might do something like this to break apart an array in an encapsulated way:

(function($user){
   extract($user);
   echo "<p>$first_name $last_name</p>";
   ...
})();

I see Blade offers subviews, which may be useful in some contexts, but for others it may prove overkill.


#63

It is possible to use extract in Blade templates. I just do this

@if ($postData)
  @php(extract($postData))
@endif

Might be better ways but this works


#64

Anyone tried the @yield and @extends blade functions? Can they be used with sage 9?


#65

Not sure why they wouldn’t work. Each of the templates already uses @extends: https://github.com/roots/sage/blob/master/templates/single.blade.php#L1

@extends basically replaces the theme wrapper.


#66

This is brilliant. Thank you for your work.


#67

Maybe by default make it pull all files from controllers directory, but allow for the data to be filtered.


#68

Another option would be to provide a separate method for pulling an array of all the files in the controllers directory which one could use to populate the controllers array. Makes it a little more clear what’s happening.


#69

With the soberwp/controller plugin, I’m wondering if it would be a wise setup to have controllers for specific components of a fairly complex page. So break up the page into partials, and then create a controller for each specific partial. On the main blade template I would then include all of the partials. How is everyone else breaking up large, complex pages with their controllers and templates?


#70

“Controllers” usually corresponds to a single page/route, not per partial.


#71

I’m surprised nobody pointed it out sooner but Laravel 5.4 was released at the end of January and Blade got a new feature.

I posted an issue on the Sage tracker to get this updated for everyone, but manually bumping the version of both illuminate packages in composer.json to ~5.4.0 and running composer update worked fine for me after clearing Blade’s cache.

Components seem really nice and should help a good bit with organization in complex themes. They also accept data through an array or using the new @slot directive.

I can see a great use for this with things such as sliders, alerts, forms, various widgets, etc. used throughout the theme as well as breaking down complex partials into a component-based partial making it easier to maintain.

I went the route of creating a components folder inside of templates.

A generic use-case (which is also the example given on the Blade docs) would be alerts.

Example

/templates/components/alert.blade.php

<div class="alert alert-warning">
  {{ $slot }}
</div>

/templates/partials/example.blade.php

@component('components.alert')
  {{ __('Sorry, no results were found.', 'sage') }}
@endcomponent

This can be made more complex using the @slot directive or by passing an array of data to @component.

Example 2

/templates/components/alert.blade.php

<div class="alert alert-warning">
  <div class="alert-title">{{ $title }}</div>
  
  {{ $slot }}
</div>

/templates/partials/example.blade.php

@component('components.alert', ['title' => 'Warning'])
  {{ __('Sorry, no results were found.', 'sage') }}
@endcomponent

#72

I’m not sure if this is the right place to ask this, so let me know if this is improper and I’ll make a new topic.

I recently found out that, in Sage 9, Blade is setup to compile templates to PHP files and write them to the media uploads folder. If the file changes, Blade will recompile the file and write the update to the cache. If the file has not changed, and it already exists, it will be loaded from the cache.

I think that’s great that it has a cache. It saves CPU and makes sense.

However, I’m wondering if there’s a way to precompile the cache when I deploy to the server, rather than the default behaviour of checking upon page request.

I found this out because I’m using a plugin to offload the media uploads to s3, and it caused pages to stop loading (white screen of death). The blade cache was being offloaded to s3, and then could not be loaded because allow_url_include is (and definitely should be!) disabled, so PHP from remote servers cannot be executed. So I had to change the directory where Blade stores its compiled templates to ensure it’s stored and loaded locally. (For me, the config to change it was at /src/setup.php:127, changing view.compiled to WP_CONTENT_DIR . "/uploads/cache/compiled" instead of "{$paths['dir.upload']}/cache/compiled").

It would make a lot more sense to be able to precompile the templates. They aren’t going to change between deploys, and then I can set my file system to truly be read-only and harden it up.

Is there a way to force Blade to precompile the files upon deploy and stop the compile-on-request behaviour? I tried looking at Laravel’s docs and searching the web and couldn’t find anything about this.


#73

I reworked the plugin a bit since the alpha, not sure if you’re tracking, but it now works on page/route.

I’ve made it implement the same hierarchy as WordPress templates so you don’t have to duplicate controllers if for example single.blade.php and page.blade.php have the same data. You could just use src/controllers/singular.php to pass to both. It also enables you to inherit data from the controller hierarchy (if you want, it overrides by default) and you can use src/controllers/base.php for global vars.

You can include partials/components data by using standard PHP traits. You can view the docs on the github readme which explains it better, but it makes it easier to reason about.


#74

That’s a really good question.

I found a compile method. Maybe we can write a Composer script to precompile all templates.

edit: I opened an issue: https://github.com/roots/sage/issues/1851


#75

Thanks @swalkinshaw. It would make me so happy to have this feature! :thumbsup:


#76

I wrote a very simple WP CLI package to do this: https://github.com/alwaysblank/blade-generate There are probably a ton of ways to improve on it, but in the short term anyone should be able to hook this into a deploy script and get the desired effect.


#77

@withjacoby your controller plugin looks awesome and I want to try it.

Two stupid questions… I can’t install it following the instructions composer require soberwp/controller. Not found. Do I need to add the repository to composer somehow?

I’m my custom controller in my project I run add_action('the_post', function ($post_object) { ... });

This is not optimal because it runs multiple times per page load but it was easiest for me while learning blade… How would a similar controller look using the plugin. What I’m trying to achieve is fetching data for different post types not just at single pages but also when in custom loops.

Thanks!


#78

Is there a way to load the plugin without it being a WordPress plugin? I mean, is it possible to autoload it just like sage’s src/lib/Sage?


#79

EDIT: You can now use composer require soberwp/controller:dev-master

I’m not sure I understand your use case, but I would create a custom controller for the archive pages. So you would have src/controllers/archive-{post_type}.php and pass the data through that. If you wanted to pass to the post type archive page and single page you could create a component and include in each controller.

I’m not sure that answers your question?


#80

This seems to be working for me, but haven’t done much testing so let me know if it throws an error, if so, you can create a github issue.

Place all the plugin files in src/lib/Sober/Controller/

Include somewhere in functions.php

include_once get_stylesheet_directory() . '/src/lib/Sober/Controller/controller.php';