Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: expose methodName via CAPPluginCall #7476

Closed
1 of 3 tasks
robingenz opened this issue May 21, 2024 · 4 comments · Fixed by #7641
Closed
1 of 3 tasks

[Feature]: expose methodName via CAPPluginCall #7476

robingenz opened this issue May 21, 2024 · 4 comments · Fixed by #7641
Assignees
Labels

Comments

@robingenz
Copy link
Contributor

Description

Expose the method name of the plugin method that was called.

Platforms

  • iOS
  • Android
  • Web

Request or proposed solution

On Android, we can call getMethodName() to get the method name of the plugin method that was called.
On iOS, there is no such method/property. It would be great if there was a methodName property in CAPPluginCall.

Alternatives

No response

Additional Information

No response

@robingenz
Copy link
Contributor Author

Would a PR be welcome?

@markemer
Copy link
Member

markemer commented Sep 3, 2024

Would a PR be welcome?

Yeah, this seems reasonable - I just don't know when I can get to it, so a PR would be great.

@robingenz
Copy link
Contributor Author

Yeah, this seems reasonable - I just don't know when I can get to it, so a PR would be great.

Done: #7641

Copy link

ionitron-bot bot commented Oct 27, 2024

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out.

@ionitron-bot ionitron-bot bot locked and limited conversation to collaborators Oct 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants