feat: platform.is should accept multiple values

[davidecampello]

Prerequisites

• [X] I have read the Contributing Guidelines.
• [X] I agree to follow the Code of Conduct.
• [X] I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request

I think platform.is should accept multiple values to help avoid multiple call with or

Describe the Use Case

this.platform.is('desktop', 'mobileweb', ...) instad of this.platform.is('desktop') || this.platform.is('mobileweb')

Describe Preferred Solution

No response

Describe Alternatives

No response

Related Code

No response

Additional Information

No response

[liamdebeasi]

Thanks for the issue. Can you provide a use case for this feature? Also, what do you think the platform.is call should return when passing in multiple values? Would you expect it to return true only if all of the conditions are met, or would you expect it to allow for partial matching?

[indraraj26]

if all are matched then it should return true otherwise if you want allow if one of the matched then you can use old way as we have been using with OR operator

[davidecampello]

In my case I would like to have a OR operator between all passed parameters but maybe a good solution can be have tho methods:

anyMatch(...platform: Array<Platform>): boolean
allMatch(...platform: Array<Platform>): boolean

or maybe we can call "every" and "some", like in javascript Array

But for retrocompatibility this is not a good option...

In my case I have an app that use capacitor-community/barcode-scanner and I need to open a modal instead of the plugin only if platform is desktop and mobileweb so I tought to suggest this update and generally I prefer to write a code like this.platform.is('desktop', 'mobileweb', ...) instad of this.platform.is('desktop') || this.platform.is('mobileweb') but I'm aware this is not a very important thing. I can also create a small utility in my app.

Thanks

[liamdebeasi]

Thanks! I can talk with the team about this feature.

[liamdebeasi]

I discussed this with the team, and we think this is a valuable feature to add to Ionic. No ETA on implementation, but I will update this thread when I have more to share.