Skip to content

Fixes to get to dokieli compatiblity#34

Open
ylebre wants to merge 5 commits into
mainfrom
feature/dokieli-compat
Open

Fixes to get to dokieli compatiblity#34
ylebre wants to merge 5 commits into
mainfrom
feature/dokieli-compat

Conversation

@ylebre

@ylebre ylebre commented Jun 22, 2026

Copy link
Copy Markdown
Member

This branch contains the fixes go make things work with Dokie.li

@ylebre ylebre requested a review from Potherca June 22, 2026 14:48
Packagist no longer support re-tagging a release.

Since the v0.14.0 release has been removed, v0.14.0 has been re-tagged as v0.14.1.
if (preg_match("/^http(s)?:/", $clientId)) {
$clientData = self::getRemoteRegistration($clientId);
if (!isset($clientData['origin']) && isset($clientData['client_uri'])) {
$clientData['origin'] = preg_replace("/\/$/", "", $clientData['client_uri']);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer rtrim to using a RegExp:

$clientData['origin'] = rtrim($clientData['client_uri'], '/');

@Potherca Potherca left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing functionally wrong.

One nitpick, feel free to resolve or ignore at will.

I've added a commit to bump the solid-auth version, as Packagist no longer allows re-tagging releases. See https://packagist.org/about/version-immutability.

(Release v0.14.0 and v0.14.1 are both tags on the same commit.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants