Update uses of new Post

Author: Tom Mitchelmore

docs/README.md

@@ -26,8 +26,9 @@ class IndexController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $context['posts'] = Post::whereStatus('publish')
+        $context = Timber::context();
+        $context['posts'] = Post::builder()
+            ->whereStatus('publish')
             ->limit(5)
             ->get();
 

docs/the-basics/post-types.md

@@ -9,18 +9,23 @@ sidebar_position: 4
 Typically in WordPress when you're querying posts you get [`WP_Post`](https://codex.wordpress.org/Class_Reference/WP_Post) objects back. Timber have taken this a step further and return a `Timber/Post` object instead. This [has a ton of great helper methods and properties](https://timber.github.io/docs/reference/timber-post/) which makes it easier and more expressive to use.
 
 ```php
-use Timber\Post;
-
-$post = new Post(1);
-$posts = Timber::get_posts($wpQueryArray);
+$post = Timber::get_post(1); // \Rareloop\Lumberjack\Post
+$posts = Timber::get_posts($wpQueryArray); // \Timber\PostQuery
 ```
 
-Lumberjack has its own Post object which makes it easier and more expressive to run queries.
+:::info Note on Timber v2
+Timber v2 deprecated direct instantiation in favour of the `Timber::get_post()` factory implementation. When you call `get_post()`, Timber uses the Class Map to return the correct class for that post.
+
+**Lumberjack automatically registers your custom post types with the Timber Class Map**
+
+See: [Timber: Class Maps](https://timber.github.io/docs/v2/guides/class-maps/#the-post-class-map)
+:::
+
+Lumberjack post types provide a static `query` method to make this simpler.
 
 ```php
 use Rareloop\Lumberjack\Post;
 
-$post = new Post(1);
 $collection = Post::query($wpQueryArray);
 ```
 
@@ -29,7 +34,6 @@ This becomes especially powerful when you start registering **Custom Post Types*
 ```php
 use App\PostTypes\Product;
 
-$post = new Product(1);
 $collection = Product::query($wpQueryArray);
 ```
 

docs/the-basics/view-models.md

@@ -23,8 +23,8 @@ class SingleController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $post = new Post;
+        $context = Timber::context();
+        $post = Timber::get_post();
 
         $date = new \DateTime($post->post_date);
 
@@ -133,7 +133,6 @@ Now we can refactor our controller to use our view model instead:
 
 namespace App;
 
-use Rareloop\Lumberjack\Post;
 use Timber\Timber;
 use App\ViewModels\MediaCardViewModel;
 use Rareloop\Lumberjack\Http\Responses\TimberResponse;
@@ -142,8 +141,8 @@ class SingleController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $post = new Post;
+        $context = Timber::context();
+        $post = Timber::get_post();
 
         $context['card'] = new MediaCardViewModel($post);
 
@@ -287,7 +286,6 @@ If your view model does not know about how to get data, then you will have to fe
 
 namespace App;
 
-use Rareloop\Lumberjack\Post;
 use Timber\Timber;
 use App\ViewModels\TestimonialViewModel;
 use Rareloop\Lumberjack\Http\Responses\TimberResponse;
@@ -296,8 +294,8 @@ class SingleController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $post = new Post;
+        $context = Timber::context();
+        $post = Timber::get_post();
 
         // Get the data from somewhere, for example from ACF
         // You would have to duplicate these two lines in each controller
@@ -366,7 +364,6 @@ And we can now refactor our controller to use the named constructor like so:
 
 namespace App;
 
-use Rareloop\Lumberjack\Post;
 use Timber\Timber;
 use App\ViewModels\TestimonialViewModel;
 use Rareloop\Lumberjack\Http\Responses\TimberResponse;
@@ -375,8 +372,8 @@ class SingleController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $post = new Post;
+        $context = Timber::context();
+        $post = Timber::get_post();
 
         $context['testimonial'] = TestimonialViewModel::forPost($post);
 
@@ -391,6 +388,7 @@ And you could have the following named constructor:
 
 - `latestPosts($limit = 3)`- which knows how to get the latest _n_ posts.
 - `relatedPosts(Post $post)`- which knows how to get posts related to given post
+
   :::
 
 ## Using Hatchet

docs/the-basics/wordpress-controllers.md

@@ -18,16 +18,15 @@ In the files (i.e. controllers) that WordPress uses when it matches a route (e.g
 namespace App;
 
 use Timber\Timber;
-use Rareloop\Lumberjack\Post;
 use Rareloop\Lumberjack\Http\Responses\TimberResponse;
 
 class PageHomeController
 {
     public function handle()
     {
-        $context = Timber::get_context();
+        $context = Timber::context();
 
-        $context['post'] = new Post;
+        $context['post'] = Timber::get_post();
 
         return new TimberResponse('home', $context);
     }

versioned_docs/version-v7/README.md

@@ -26,8 +26,9 @@ class IndexController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $context['posts'] = Post::whereStatus('publish')
+        $context = Timber::context();
+        $context['posts'] = Post::builder()
+            ->whereStatus('publish')
             ->limit(5)
             ->get();
 

versioned_docs/version-v7/the-basics/post-types.md

@@ -9,18 +9,23 @@ sidebar_position: 4
 Typically in WordPress when you're querying posts you get [`WP_Post`](https://codex.wordpress.org/Class_Reference/WP_Post) objects back. Timber have taken this a step further and return a `Timber/Post` object instead. This [has a ton of great helper methods and properties](https://timber.github.io/docs/reference/timber-post/) which makes it easier and more expressive to use.
 
 ```php
-use Timber\Post;
-
-$post = new Post(1);
-$posts = Timber::get_posts($wpQueryArray);
+$post = Timber::get_post(1); // \Rareloop\Lumberjack\Post
+$posts = Timber::get_posts($wpQueryArray); // \Timber\PostQuery
 ```
 
-Lumberjack has its own Post object which makes it easier and more expressive to run queries.
+:::info Note on Timber v2
+Timber v2 deprecated direct instantiation in favour of the `Timber::get_post()` factory implementation. When you call `get_post()`, Timber uses the Class Map to return the correct class for that post.
+
+**Lumberjack automatically registers your custom post types with the Timber Class Map**
+
+See: [Timber: Class Maps](https://timber.github.io/docs/v2/guides/class-maps/#the-post-class-map)
+:::
+
+Lumberjack post types provide a static `query` method to make this simpler.
 
 ```php
 use Rareloop\Lumberjack\Post;
 
-$post = new Post(1);
 $collection = Post::query($wpQueryArray);
 ```
 
@@ -29,7 +34,6 @@ This becomes especially powerful when you start registering **Custom Post Types*
 ```php
 use App\PostTypes\Product;
 
-$post = new Product(1);
 $collection = Product::query($wpQueryArray);
 ```
 

versioned_docs/version-v7/the-basics/view-models.md

@@ -23,8 +23,8 @@ class SingleController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $post = new Post;
+        $context = Timber::context();
+        $post = Timber::get_post();
 
         $date = new \DateTime($post->post_date);
 
@@ -133,7 +133,6 @@ Now we can refactor our controller to use our view model instead:
 
 namespace App;
 
-use Rareloop\Lumberjack\Post;
 use Timber\Timber;
 use App\ViewModels\MediaCardViewModel;
 use Rareloop\Lumberjack\Http\Responses\TimberResponse;
@@ -142,8 +141,8 @@ class SingleController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $post = new Post;
+        $context = Timber::context();
+        $post = Timber::get_post();
 
         $context['card'] = new MediaCardViewModel($post);
 
@@ -287,7 +286,6 @@ If your view model does not know about how to get data, then you will have to fe
 
 namespace App;
 
-use Rareloop\Lumberjack\Post;
 use Timber\Timber;
 use App\ViewModels\TestimonialViewModel;
 use Rareloop\Lumberjack\Http\Responses\TimberResponse;
@@ -296,8 +294,8 @@ class SingleController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $post = new Post;
+        $context = Timber::context();
+        $post = Timber::get_post();
 
         // Get the data from somewhere, for example from ACF
         // You would have to duplicate these two lines in each controller
@@ -366,7 +364,6 @@ And we can now refactor our controller to use the named constructor like so:
 
 namespace App;
 
-use Rareloop\Lumberjack\Post;
 use Timber\Timber;
 use App\ViewModels\TestimonialViewModel;
 use Rareloop\Lumberjack\Http\Responses\TimberResponse;
@@ -375,8 +372,8 @@ class SingleController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $post = new Post;
+        $context = Timber::context();
+        $post = Timber::get_post();
 
         $context['testimonial'] = TestimonialViewModel::forPost($post);
 
@@ -391,6 +388,7 @@ And you could have the following named constructor:
 
 - `latestPosts($limit = 3)`- which knows how to get the latest _n_ posts.
 - `relatedPosts(Post $post)`- which knows how to get posts related to given post
+
   :::
 
 ## Using Hatchet

versioned_docs/version-v7/the-basics/wordpress-controllers.md

@@ -18,16 +18,15 @@ In the files (i.e. controllers) that WordPress uses when it matches a route (e.g
 namespace App;
 
 use Timber\Timber;
-use Rareloop\Lumberjack\Post;
 use Rareloop\Lumberjack\Http\Responses\TimberResponse;
 
 class PageHomeController
 {
     public function handle()
     {
-        $context = Timber::get_context();
+        $context = Timber::context();
 
-        $context['post'] = new Post;
+        $context['post'] = Timber::get_post();
 
         return new TimberResponse('home', $context);
     }

versioned_docs/version-v8/README.md

@@ -26,8 +26,9 @@ class IndexController
 {
     public function handle()
     {
-        $context = Timber::get_context();
-        $context['posts'] = Post::whereStatus('publish')
+        $context = Timber::context();
+        $context['posts'] = Post::builder()
+            ->whereStatus('publish')
             ->limit(5)
             ->get();
 

versioned_docs/version-v8/the-basics/post-types.md

@@ -9,18 +9,23 @@ sidebar_position: 4
 Typically in WordPress when you're querying posts you get [`WP_Post`](https://codex.wordpress.org/Class_Reference/WP_Post) objects back. Timber have taken this a step further and return a `Timber/Post` object instead. This [has a ton of great helper methods and properties](https://timber.github.io/docs/reference/timber-post/) which makes it easier and more expressive to use.
 
 ```php
-use Timber\Post;
-
-$post = new Post(1);
-$posts = Timber::get_posts($wpQueryArray);
+$post = Timber::get_post(1); // \Rareloop\Lumberjack\Post
+$posts = Timber::get_posts($wpQueryArray); // \Timber\PostQuery
 ```
 
-Lumberjack has its own Post object which makes it easier and more expressive to run queries.
+:::info Note on Timber v2
+Timber v2 deprecated direct instantiation in favour of the `Timber::get_post()` factory implementation. When you call `get_post()`, Timber uses the Class Map to return the correct class for that post.
+
+**Lumberjack automatically registers your custom post types with the Timber Class Map**
+
+See: [Timber: Class Maps](https://timber.github.io/docs/v2/guides/class-maps/#the-post-class-map)
+:::
+
+Lumberjack post types provide a static `query` method to make this simpler.
 
 ```php
 use Rareloop\Lumberjack\Post;
 
-$post = new Post(1);
 $collection = Post::query($wpQueryArray);
 ```
 
@@ -29,7 +34,6 @@ This becomes especially powerful when you start registering **Custom Post Types*
 ```php
 use App\PostTypes\Product;
 
-$post = new Product(1);
 $collection = Product::query($wpQueryArray);
 ```