Do yu have debugbar installed?

Something like that… but more so any complete project…

yes, it is not bad to write the next one firstOrFail too..

i did it too

not necessary

anyways do it as you like

I dont use this way, its not clean coding and not fit to what you really want to do

I would do it only one line

do yu have debugbar installed ?

one line?

how?

no

so thats why you will never understand what I mean 🙂

Telescope isnt good?

I didnt say that its bad, but why should I use instead debugbar 🙂

How do you write it in one line?

for query optimization, to see how many queries running to fetch all data, bla bla

👍🤦‍♂️I forgot it,

I will install it tomorrow, I have just finished my work

$post = Post::with(‘category’)->whereSlug($slug)->firstOrFail();

and I would write a scope inside Post model to fetch similar posts

and use it by single query

I have one post and the related posts then I did two variables…

so its not really necessary to have separate queries

you know what scope is ?

No🤔

so thats why 2 lines you write 🙂

It does what I want?

this gets only the post with his related category

but the related posts is not in here.

for related posts in post model you should create a public function

something like;

public function scopeSimilarPosts($query) {
return self::whereCategoryId($query->category_id)->get();
}

then call it in view, foreach ( $post->similiarPosts() as $single) { … }

Ok, wait.

and even you can set another relationship to Post hasMany Post according to category_id to category_id

something like that

there are several methods you can use

depends performance issues you can pick the one suits for you

I have got a category_id in posts table, but why such error?

your scope is not the way I wrote

you querying the single post which is returned,

and trying to get() of a single post

same error

well do it the way you like

First do it, them do it right, don’t try to get from 0 to 100, and get half baked knowledge in the way.

ok, sorry bro