Leonid Meleshin

Totally agreed! Such behaviour already exists for relationships counts, and just have to exist on relationships themselves https://laravel.com/docs/8.x/eloquent-relationships#counting-related-models

@dele-corporate yeah, there are still some things to do, I'll try to find my time to finish all on weekend

> It would be awesome if this could get merged. Can we help @leon0399 ? the only real thing left to do, is Readme and some final testing, but I...

@danchristian this is **NOT** SSR. This approach completely removes all contents from server-side-render, and leaves rendering to client. It means no performance advantages and no crawler would be able to...

For documentation deployment, I think Github's Wiki isn't great solution, since documentation should be versioned. Personally, I think it would be great to use Pages for deployment, and some tools...

Don't think we need special issue for documentation roadmap. I see our current steps following: - [x] Find our way to deploy *current* documentation somewhere (https://github.com/PHP-Open-Source-Saver/jwt-auth/issues/61) - [ ] Update...

> We should keep both because the alg encrypt, in fact as per what I was reading (I'm having some JWS issues here in my job) this is something related...

@mfn as we discussed in #78 I've enabled coverage report. It will only comment if coverage was actually changed. I also updated to latest action version, since prev one was...

> @leon0399 LGTM! > > Is the codecov comment so verbose because it was "just enabled" [#92 (comment)](https://github.com/PHP-Open-Source-Saver/jwt-auth/pull/92#issuecomment-1001655914) ? No, we actually can configure which parts of report we need...

> Is the "graphic" useful? > > Is showing files at 100% really useful? > > I suggest to trim it down to what is truly additional + beneficial +...