Support wildcard in option ignore-platform-req #10045
Comments
|
So basically you want Seems reasonable to me, if this kind of wildcard syntax can be parsed into some PHP comparison checks etc. |
|
@dereuromark Exactly! Basically, we need |
|
Maybe also the opposite could be useful then for your case, using Just spitballing some ideas here for the team to assess. A comma separated list is already supported or not? To combine |
|
@dereuromark My tests have shown that a comma separated list is not yet supported. Correct me If I am wrong, but running on its own would be useless, since all platform requirements are checked by default. It would make sense, e.g. by running or combined with |
|
a comma separated list is indeed not supported. To pass multiple values, you need to repeat the |
|
Sure, this was just spitballing some ideas. Would sure be trivial to add and quite useful over the repeating of such config. But I don't want to derail too much, the initial topic was still about wildcard support, not making multiple values easier. |
|
It's technically feasible I suppose, to add wildcard support. I am not sure it's really worth it though. If you are interested in sending a PR.. I think replacing the array|bool for $ignorePlatformReqs in Solver and AutoloadGenerator by a PlatformRequirementFilter object which would contain the list and patterns to ignore and then have methods to check if X is ignored, or if all is ignored (the current |
|
@Seldaek Thanks for your feedback! Our actual goal is to update packages, checking only the PHP version requirement. With a wildcard support, it would be possible, because we could directly exclude all extensions at once. We would also appreciate any other solution supporting our use case, e.g.: would be a great alternative for us. |
|
Yeah perhaps we could make it a special |
|
Oh, I have the exact same (Renovate) use-case and therefore a high personal interest in this feature. I will take a look at this until next week or so, I wanted to learn more about Composer internals anyways. |
Introduces a PlatformRequirementFilter with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in composer#10045 but without changing behaviour. The idea behind this is to be able to adapt simple wildcard or regex ignores in a follow-up.
Introduces a `PlatformRequirementFilter` with methods that help to decide if a requirement is ignored or not as discussed in #10045 but without changing behaviour.
When installing or updating packages, it would be useful if all platform requirements could be ignored, except for PHP.
Currently, this is only possible by ignoring each extension individually, e.g.:
composer update --ignore-platform-req=ext-json --ignore-platform-req=ext-xmlor by faking platform requirements in
config.platform, e.g.:We have this use case when updating composer projects with Renovate. See details in linked issue(s).
So the subject of this issue could also be:
Installing Composer dependencies in environments without valid platform requirements while respecting the PHP version requirement
Related:
The text was updated successfully, but these errors were encountered: