Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123959
Precedence: bulk
MIME-Version: 1.0
References: <CAEUnE0fGZ3jFiBG=GyvnhBzH5a0iO4=n75PM=3+6zLAMrumEvA@mail.gmail.com>
 <CADK1yX+E9mvaM_CHJ8tmEx=O70hf8xasbvngh4wvNM8ce8KKGQ@mail.gmail.com>
 <CAEUnE0cnh_fytD=LUQrLgpZHMX4oyqYW21o1N-Mq39B4GqVkTg@mail.gmail.com> <CAEUnE0c+tmKHB6ZvsQtWCyi+RYfoBdqHoWEz-LXsi8tZn+jDhQ@mail.gmail.com>
In-Reply-To: <CAEUnE0c+tmKHB6ZvsQtWCyi+RYfoBdqHoWEz-LXsi8tZn+jDhQ@mail.gmail.com>
Date: Thu, 27 Jun 2024 17:03:30 -0300
Message-ID: <CADK1yXJGcr2F2191RO4FT2-FykUF2Y7kv5MMV5caf61ALVm4JA@mail.gmail.com>
Subject: Re: [PHP-DEV] [Initial Feedback] PHP User Modules - An Adaptation of
 ES6 from JavaScript
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001b401b061be4a242"
From: deleugyn@gmail.com (Deleu)

--0000000000001b401b061be4a242
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 27, 2024 at 4:31=E2=80=AFPM Michael Morris <tendoaki@gmail.com>=
 wrote:

>
>
>> The fact there's weird behaviors as result of trying to import a file an=
d
>> suddenly a file all the way from `include_paths` or `php_modules` seems
>> like a no-go to me. I'd favor using only simple file path navigation and=
 if
>> the file doesn't exist, error.
>>
>> Perhaps if the idea gains merit, Composer could offer something similar
>> to Vite where we can create an alias to a specific folder and then impor=
t
>> things like `from '@package/path/to/file`.
>>
>
> Composer would need a massive rewrite to be a part of this since it
> currently requires the file once it determines it should do so. If we do =
a
> system where import causes the parser to act differently then that alone
> means imports can't be dealt with in the same manner as other autoloads.
>

Perhaps my point here wasn't so obvious. I wasn't talking about Composer
making drastic changes to accommodate this, I was only merely mentioning
Composer being used to provide something like the following:

```composer.json
{
    "require": {
        "php": "^8.2"
        ....
    },
    "php-modules": {
        "@packages": "./packages",
        "@utilities": "./tools/utilities"
        ....
    }
 }
```

Then whenever there's a `import Foo from '@packages/Foo.php'`, the notation
`@packages` would be replaced by the packages folder. This is equivalent to
Vite resolve.alias
https://vitejs.dev/config/shared-options.html#resolve-alias


--=20
Marco Deleu

--0000000000001b401b061be4a242
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jun 27, 2024 at 4:31=E2=80=AF=
PM Michael Morris &lt;<a href=3D"mailto:tendoaki@gmail.com">tendoaki@gmail.=
com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><div dir=3D=
"ltr">=C2=A0<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div>Th=
e fact there&#39;s weird behaviors as result of trying to import a file and=
 suddenly a file all the way from `include_paths` or `php_modules` seems li=
ke a no-go to me. I&#39;d favor using only simple file path navigation and =
if the file doesn&#39;t exist, error.=C2=A0</div><div><br></div><div>Perhap=
s if the idea gains merit, Composer could offer something similar to Vite w=
here we can create an alias to a specific folder and then import things lik=
e `from &#39;@package/path/to/file`.</div></div></div></blockquote><div><br=
></div><div>Composer would need a massive rewrite to be a part of this sinc=
e it currently requires the file once it determines it should do so. If we =
do a system where import causes the parser to act differently then that alo=
ne means imports can&#39;t be dealt with in the same manner as other autolo=
ads.</div></div></div></div></div></blockquote><div><br></div><div>Perhaps =
my point here wasn&#39;t so obvious. I wasn&#39;t talking about Composer ma=
king drastic changes to accommodate this, I was only merely mentioning Comp=
oser being used to provide something like the following:<br><br>```composer=
.json</div><div>{</div>=C2=A0 =C2=A0 &quot;require&quot;: {<br><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 &quot;php&quot;: &quot;^8.2&quot;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 ....</div><div>=C2=A0 =C2=A0 },</div><div>=C2=A0 =C2=A0 &=
quot;php-modules&quot;: {</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &quot;@pack=
ages&quot;: &quot;./packages&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 &=
quot;@utilities&quot;: &quot;./tools/utilities&quot;</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 ....</div><div>=C2=A0 =C2=A0 }</div><div>=C2=A0}<br></div=
><div>```</div><div><br></div><div>Then whenever there&#39;s a `import Foo =
from &#39;@packages/Foo.php&#39;`, the notation `@packages` would be replac=
ed by the packages folder. This is equivalent to Vite=C2=A0resolve.alias=C2=
=A0<a href=3D"https://vitejs.dev/config/shared-options.html#resolve-alias">=
https://vitejs.dev/config/shared-options.html#resolve-alias</a></div></div>=
<br clear=3D"all"><div><br></div><span class=3D"gmail_signature_prefix">-- =
</span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div=
 dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D=
"ltr"><div dir=3D"ltr">Marco Deleu</div></div></div></div></div></div></div=
></div></div>

--0000000000001b401b061be4a242--