syntax error, unexpected '|', expecting variable (T_VARIABLE)

It is safer to specify the platform requirement you would like to ignore using the --ignore-platform-req option of Composer v2:

composer install --ignore-platform-req=ext-pcntl

I added a script to composer.json to ease this:

As seen above, to ignore multiple platform requirements you use the `–ignore-platform-req` multiple times.

Further reading

• How to install Composer packages ignoring PHP version requirements

• Stackoverflow answer - A new feature in Composer v2 allows you to selectively ignore platform requirements

• Composer v2 documentation

composer require laravel/horizon "^4.0".

If you are using Windows and get the error Problem 1 - laravel/horizon[v4.0.0, ..., 4.x-dev] require ext-pcntl * -> it is missing from your system. Install or enable PHP's pcntl extension. - Root composer.json requires laravel/horizon ^4.0 -> satisfiable by laravel/horizon[v4.0.0, ..., 4.x-dev]., use the below command instead:

composer require laravel/horizon "^4.0" --ignore-platform-reqs

Also note that from this point on when using Windows, you may have to add --ignore-platform-reqs on all subsequent composer commands if not they will fail. See this Stackoverflow answer if you will like to skip adding this every time.

Initial attempts using whereDate() all gave inaccurate results.

<?php

ModelName::query()
    ->whereDate(
        'created_at',
        '>=',
        (new Carbon('first day of last month'))->toDateString()
    )
    ->whereDate(
        'created_at',
        '<=',
        now()->subMonthNoOverflow()
    )
    ->get();

I later found out whereDate() converts the date to the format 'Y-m-d' so the time is not considered (see below).

<?php

public function whereDate($column, $operator, $value = null, $boolean = 'and')
{
    // ...
    if ($value instanceof DateTimeInterface) {
        $value = $value->format('Y-m-d');
    }
    // ...
}

Using whereBetween() did the trick though! It worked exactly as wanted it to.

<?php

ModelName::query()
    ->whereBetween(
        'created_at',
        [
            (new Carbon('first day of last month'))->toDateString(),
            now()->subMonthNoOverflow()
        ]
    )
    ->get();

Further reading

• How to query between two dates using Laravel and Eloquent? - Stackoverflow
• MySQL SELECT WHERE datetime matches day (and not necessarily time) - Stackoverflow
• whereBetween - Laravel Docs
• whereDate - Laravel Docs

If you make a normal request like:

$response = Http::post(...);

You will always be returned an Illuminate\Http\Client\Response object, even if a server error or timeout occurs.

However, if you would like you request retried 3 times as below,

$response = Http::retry(3, 100)->post(...);

an exception will be thrown if the 3 attempts fail, or a timeout occurs. But I just want the response object returned, and after inspecting the exception thrown after the retries, I noticed the response object is attached to it. So I wrote this:

$response = rescue(function () {

    return Http::retry(3, 100)->post(...);

}, function ($e) {
    
    return $e->response;

});

With the above rescue() wrapper around the HTTP request, I always receive a response object and can safely go ahead to verify its status.

$response->successful() : bool;
$response->failed() : bool;
$response->serverError() : bool;
$response->clientError() : bool;

Hope this was helpful ;-).

<div>

    <form wire:submit.prevent="submit">

        <div class="form-group">
            
            <input wire:model="username"
                   type="text"
                   name="username"
                   placeholder="Username"
                   value="{{ old('username') }}"
                   class="form-control" />

            @error('username') <span class="text-danger">{{ $message }}</span> @enderror
        </div>

        <button onclick="confirm('Are you sure?!') || event.preventDefault();"
                type="submit">
            Submit
        </button>

    </form>
    
</div>

The most relevant piece being the addition of onclick="confirm('Are you sure?!') || event.preventDefault();" to the submit button. Also, notice the use of event.preventDefault() instead of event.stopImmediatePropagation() as you probably might have seen in many blog posts as well as the Livewire documentation. Something like this:

<button onclick="confirm('Are you sure?!') || event.stopImmediatePropagation();"
        type="submit">
    Submit
</button>

For the use case of confirming a form submission, event.stopImmediatePropagation() doesn’t stop the submit action even if the user does not confirm the operation. event.preventDefault() does the trick.

event.stopImmediatePropagation() however works perfectly when you are only handling a click event on the button, no submit event.

<form>
    <input type="text"
           name="code"
           data-cy="code">
                                
    <input type="tel"
           name="phone"
           data-cy="phone">
</form>

Using Cypress’s API methods

If you need to hold a reference to the value, you can query it using one of the methods below.

cy.get('[data-cy=code]').should(($input) => {
  const value = $input.val();
    
  console.log(value); // do something with the value
    
})

cy.get('[data-cy=code]').invoke('val').should((value) => {

    console.log(value);

})

Querying the DOM

You can also retrieve an input’s value by querying the DOM directly.

cy.document().then((doc) => {
    const value = doc.querySelector('[data-cy=code]').value;
    
    console.log(value);
});

Note that to access the test page’s document, we have to use the cy.document() command to obtain a reference. The document you access as a global belongs to the Cypress runner, but the test page is inside an iFrame which has a different document reference.

Further reading

• How do I get an input’s value? - Cypress Documentation
• document.querySelectorAll doesn’t work in cypress - Stackoverflow

<a href="./assets/vcards/mtn.vcf"
   data-cy="mtn-vcard"
   download>
    Download MTN Vcard
</a>
<a href="./assets/vcards/orange.vcf"
   data-cy="orange-vcard"
   download>
    Download Orange Vcard
</a>

Here’s how I would accomplish this with Cypress.

describe("Home page test", () => {

  it("can click on and download the MTN and Orange vcards", () => {
    cy.visit("/");

    // 0️⃣
    cy.document().then((doc) => {
      // 1️⃣
      const mtnVcardUrl = doc.querySelector('[data-cy=mtn-vcard]').getAttribute('href');
      // 2️⃣
      cy.request({
        url: mtnVcardUrl,
        encoding: 'base64'
      })
        .then((response) => {
          // 3️⃣
          expect(response.status).to.equal(200);
        });

      const orangeVcardUrl = doc.querySelector('[data-cy=orange-vcard]').getAttribute('href');
      cy.request({
        url: orangeVcardUrl,
        encoding: 'base64'
      })
        .then((response) => {
          expect(response.status).to.equal(200);
        });
    });

  })
    
});

• 0️⃣: To access your test page’s document, you should use the cy.document() command to obtain a reference. The document you access as a global belongs to the Cypress runner, but the test page is inside an iFrame which has a different document reference. Visit this Stackoverflow answer to learn more.
• 1️⃣: Query the MTN vcard and get it’s href.
• 2️⃣: Make an HTTP request with the vcard URL. For more on making http requests, visit the Cypress documentation.
• 3️⃣: Make sure the request is successful. You can further read and verify the file extension from the base64 encoded file string in the response body.

• Capacitor.getPlatform(); // ‘web’, ‘ios’, or ‘android’
• Capacitor.platform; // ‘web’, ‘ios’, or ‘android’
• Capacitor.isNative; // true or false

These work as expected, my issue is to use any of these, one has to import Capacitor, which significantly increases my web build’s bundle size.

import { Capacitor } from '@capacitor/core';

const isNative = Capacitor.isNative;

I’d like to ideally be able to check the current platform without incurring this bundle size increase, especially when I just want to check the platform and I don’t actually use Capacitor plugins etc. To fix this, I ended up using some code copied from Ionic Framework’s platform check source code on Github.

export const isNative = () => {
  return isCapacitorNative(window);
};

/**
 * @see https://github.com/ionic-team/ionic-framework/blob/master/core/src/utils/platform.ts
 */
const isCapacitorNative = (win: Window): boolean => {
  const capacitor = win['Capacitor'];
  return !!(capacitor && capacitor.isNative);
};

This still makes use of the isNative property on the Capacitor object to determine the platform, though here we don’t explicitly import Capacitor. With Capacitor always included in native builds, this should always work as expected.

Here’s a usage example.

import {RouterModule, Routes} from '@angular/router';
import {NgModule} from '@angular/core';
import {isNative} from './helpers/is-native';

export const webRoutes: Routes = [
  // Use these routes if a web app
];

const nativeRoutes: Routes = [
  // Use these routes if a native app
];

const routes = isNative() ? nativeRoutes : webRoutes;

@NgModule({
  imports: [RouterModule.forRoot(routes)],
  exports: [RouterModule],
})
export class AppRoutingModule {
}

You can check out the Ionic Framework platform check source code linked above for more granular solutions to platform checking 🔥.

For example, if a record is created now, a new one can only be created in say 10 seconds. Here’s how I did it thanks to this comment:

<?php

use Carbon\Carbon;

$interval = new DateInterval('PT10S');

$now = Carbon::now();

$nextValidCreationDate = $now->rawAdd($interval);

echo $now->toDateTimeString();
// "2020-09-30 12:42:41"
echo $nextValidCreationDate->toDateTimeString();
// "2020-09-30 12:42:51"

?>

Notice 10 seconds was added to $now. Also, notice the use of PT10S when created the DateInterval, instead of P10S which results in an error. It seems when creating time-only DateInterval objects, we have to use T too, instead of just P. When using the ISO 8601 duration format, T is the time designator that precedes the time components as explained here.

• P is the duration designator (referred to as “period”), and is always placed at the beginning of the duration.
• Y is the year designator that follows the value for the number of years.
• M is the month designator that follows the value for the number of months.
• W is the week designator that follows the value for the number of weeks.
• D is the day designator that follows the value for the number of days.
• T is the time designator that precedes the time components.
• H is the hour designator that follows the value for the number of hours.
• M is the minute designator that follows the value for the number of minutes.
• S is the second designator that follows the value for the number of seconds.

For example:

P3Y6M4DT12H30M5S

Represents a duration of three years, six months, four days, twelve hours, thirty minutes, and five seconds.

In conclusion, all date-only interval formats must start with P, e.g. P3Y, P6M, P4D, P3Y6M4D, and all time-only interval formats must start with P and T, e.g. PT12H, PT30M, PT5S, PT12H30M5S.

Here’s how I did it:

<?php

use App\Promotion;

$promotionId = Promotion::where('code', 'GOOD_DEAL')->pluck('id')->first();

echo $promotionId // 1

I tried out a good number of eloquent method combinations before arriving at pluck() + first().

With respect to the above screenshot, GOOD_DEAL_500 is a valid promotion code and GOOD_DEAL_50 is not.

Of course, I could still just use Promotion::where('code', 'GOOD_DEAL')->first()->id, but this prints out:

PHP Notice:  Trying to get property 'id' of non-object in Psy Shell code on line 1

if no promotion is found, I wanted to avoid this 🤷🏻‍♂️.