Eric MORAND

@stof > Whitespace control happens at the lexer level. Which is wrong and should have been fixed years ago. - I'm sure it was mentioned already at least by myself....

> composer.json supports declaring dependencies on PHP extensions as well (by depending on ext-intl). I propose we add that dependency, which would make composer.json complain directly when installing. Wouldn't that...

@xabbuh > If you don't care about your environment being able to actually run the code, you can instruct Composer to ignore them with the `--ignore-platform-reqs` option. I know, and...

Allow me to bump this issue: is there are reason about that? Is it a bug, or is it a deliberate choice?

Make sense. Does it mean that destructuring section does not apply to class instances ?

Can you explain the _why_ ? Where do you draw the line between what is named Object in the documentation, and what you name Class instance? Aren't class instances _objects_?...

> Also, import { doSomething } is not destructuring, it's a named import, which is something quite different. My example was wrong, sorry. ```mjs import {service} from "./service.mjs"; const {doSomething}...

Also, I'm curious about what you mean by "You always have to know **what** a thing you're importing is". The **what** is the type, the interface, the shape of the...

> in all programming, everywhere, without exception, you have to know what you're importing Yes, _what_. Not _how_. > You can do that by reading docs, by reading the source...

Shouldn't Portainer _not_ check for origins at all? I mean, trusted origins are the infrastructure layer responsibility, not the application layer one. If one wants to restrict the origins that...