Convert HEIC Images to JPEG in PHP

The php-heic-to-jpg PHP package is the easiest way to convert HEIC (High-Efficiency Image Container) images to JPEG with PHP and Laravel framework. The post Convert HEIC Images to JPEG in PHP appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ---
http://dlvr.it/SmSrNp

Read More

Laravel 10.7 Released

Laravel 10.7 added pipe() to run commands in sequence, setValue() to Validator, and the ability to assert invokable event listeners in tests. The post Laravel 10.7 Released appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ---
http://dlvr.it/SmPsvd

Read More

Useful Laravel Date Scopes for Eloquent Models

The Laravel Date Scopes package provides some helpful query scopes for your Laravel Eloquent models. The post Useful Laravel Date Scopes for Eloquent Models appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ---
http://dlvr.it/SmLvFd

Read More

The Best Practices Guide to OpenTelemetry for Developers

OpenTelemetry is a free and open-source software initiative with the objective of supplying software developers with the means to create distributed systems. The post The Best Practices Guide to OpenTelemetry for Developers appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ---
http://dlvr.it/SmHy06

Read More

Laravel Date Scopes

Hi Laravel artisans, checkout our new package with a useful range of date scopes for your Eloquent models! https://github.com/laracraft-tech/laravel-date-scopes Basically it allows you to query any kinds of date ranges like: Transaction::ofLast60Minutes(); // query transactions created during the last 60 minutes Transaction::ofToday(); // query transactions created today Transaction::ofYesterday(); // query transactions created yesterday Transaction::ofLastWeek(); // query transactions created during the last week Transaction::ofLastMonth(); // query transactions created during the last month Transaction::ofLastQuarter(); // query transactions created during the last quarter Transaction::ofLastYear(); // query transactions created during the last year ... submitted by /u/Nodohx [link] [comments]
http://dlvr.it/SmFKtM

Read More

Possible to switch from Laravel/UI easily?

Can Laravel Auth scaffolding be easily changed from from one frontend framework to another without causing too much of a mess? How late is too late? Can I do this further into development, or is this kind of design decision something that should be made early. I'm just trying to get an understanding of the flexibility here. Thank you! submitted by /u/AtumTheCreator [link] [comments]
http://dlvr.it/SmCNcZ

Read More

Let's talk about Form Requests

Form Requests are best known for validation logic that will pre-validate for you. They are fantastic, and I lean on them heavily all the time. The post Let's talk about Form Requests appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ---
http://dlvr.it/Sm9Q0l

Read More

Laravel Expectations Plugin for Pest

Pest Laravel Expectations is a Pest plugin that adds Laravel-specific expectations to the testing ecosystem. The post Laravel Expectations Plugin for Pest appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ---
http://dlvr.it/Sm6szR

Read More

laravel observers, whats the rule of thumb?

After reading the replies of this tweet I got confused cuz some people mention that the first query won't trigger the eloquent observers, why is the first query different from the second one? I always thought they were the same thing and there weren't any significant differences ​ https://preview.redd.it/l2ap1x8pl6sa1.png?width=1013&format=png&auto=webp&s=1b3db38fc0183bf008d42de15dbda927394fd315 submitted by /u/mrdingopingo [link] [comments]
http://dlvr.it/Sm45LN

Read More

Java Open Telemetry Class Loading Issue

I have a spring boot java project, which has a open telemetry jar. The service is packaged as a docker image and it is deployed on Kubernetes. When the service starts, this open telemetry jar tries to instantiate okHttpClient internally and fails. This instantiation in the open telemetry jar doesn't seem have retry limits, so it tries to load the class repeatedly. Eventually, the service shutsdown with OutOfMemoryError. This behavior is sporadic. For eg - if there are multiple instances of the service running, occasionally 1 or 2 instances fail with this error. But when these instances are killed and restarted the issue doesn't come up again. Also, the issue could not be replicated in the developer machines. Can someone please give me pointers on how to debug this issue?
http://dlvr.it/Sm387H

Read More

Pest Architecture Plugin

 With the release of PestPHP v2, we can now test the architecture of our applications. In this tutorial, we will walk through how to use this plugin.

It starts with creating an ArchTest.php file under tests/Feature in our application. From here, we can begin documenting our architectural requirements and rules - allowing us to test these with a great API and fantastic developer experience.

One test I recommend adding to your tests will ensure no stray debugging calls are left in our application.

test('Not debugging statements are left in our code.')
 ->expect(['dd', 'dump', 'ray'])
 ->not->toBeUsed();

Before we go too deeply into the available rules we could use, let's analyze the structure of these tests. It starts with a test call, where we define the name of the test - make sure this is something understandable that describes what you are testing for. We then use Pest higher-order expectations API to declare what we are testing. We start by expecting something. In the above case, we expect none of the following to be used, or we could expect something to appear.

Next, let's look at more specific tests we can create to ensure our architectural rules are followed. Obviously, the first thing we need to do is ensure we understand what our architectural practices are. You can't simply implement rules you don't intend to follow. During this tutorial, I will document some rules I like to apply to my projects. Being an un-opinionated developer as I am.

test('Our API controllers return responses that we expect')
    ->expect('Illuminate\Contracts\Support\Http\Responsable')
    ->toBeUsedIn('App\Http\Controllers\Api');

In this test, we want to ensure that we use Response classes in our API. Our Controllers should return Responsable classes so that we minimize code duplication and always return in a standard way.

test('We do not directly use Eloquent Models in our APIs.')
    ->expect('App\Models')
    ->not->toBeUsedIn('App\Http\Controllers\Api');

In this test, we want to ensure that we do not directly use Eloquent models in our API. We should use Action, Command, Query, or Service/Repository classes when working with the database. This is a rule I like to follow as much as possible as, again, it reduces code duplication.

test('We always use Resouce classes when responding')
    ->expect('App\Http\Resources')
    ->toBeUsedIn('App\Http\Controllers\Api');

In this test, we want to ensure we always use Resource classes in our controllers. This allows us to ensure that we have a standardized way to return data from the API.

The following rules will be more specific to how I code, so it may not be relevant to you - but it shows particular ways you can test the modular aspects of your code.

I lean heavily on my modular approach to Laravel, using separate namespaces where I need them. I also lean heavily on Commands for write actions and Queries for read actions. I can ensure that these are used where it makes sense to me.

test('We use Query classes where we need them in the Catalog domain')
    ->expect('Domains\Catalog\Queries')
    ->toBeUsedIn('App\Http\Controllers\Api\V1\Products\Read');

This is currently something that I would use as a temporary measure until the architecture plugin supports wildcards. We want to make sure that We are using queries in the right place. As soon as we allow wildcards in the architecture plugin, we can do something like this:

test('Query classes are used for read operations')
    ->expect('Domains\*\Queries')
    ->toBeUsedIn('App\Http\Controllers\Api\*\*\IndexController')
    ->toBeUsedIn('App\Http\Controllers\Api\*\*\ShowController')
    ->not->toBeUsedIn('App\Http\Controllers\Api\*\*\StoreController')
    ->not->toBeUsedIn('App\Http\Controllers\Api\*\*\UpdateController')
    ->not->toBeUsedIn('App\Http\Controllers\Api\*\*\DeleteController');

With this test, we can ensure that we are using queries in all of our read endpoints but not the write endpoints, allowing us to keep a tighter grip on our code architecture and approach.

Of course, this is not available right now, but perhaps it will allow us to have fewer architectural rules and the same amount of coverage in the future.

Read More

http://dlvr.it/SlgtJl

Read More

Laravel Ciphersweet is a package by Spatie

Laravel Ciphersweet is a package by Spatie to integrate searchable field-level encryption in Laravel applications. The package's readme explains the problem Ciphersweet can help solve as follows:In your project, you might store sensitive personal data in your database. Should an unauthorised person get access to your DB, all sensitive can be read which is obviously not good.To solve this problem, you can encrypt the personal dat
http://dlvr.it/SlgMrb

Read More