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] Know exact type/format[url/Contact/Phone/SMS/Text] of data provided by QR #366

Closed
Priyank-Sharma-89 opened this issue Jul 14, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@Priyank-Sharma-89
Copy link

Is your feature request related to a problem? Please describe.
I created a practice app to implement QR scan feature. On the website from where I am generating QR, I see lot of tabs for different and specific types of data, like URL, text, Contact, SMS, Phone. However, when I tried with every type data, QR scan only returns "string" type data. I faced difficulties, specifically to identify if its a Contact or email. Also, if its a string just with digits/numbers (in case of phone) or normal text.

Even barcode.format.formatName is returning QR_CODE for all type of data.

Describe the solution you'd like
Can we have something like barcode.code.format.url or barcode.code.format.VCARD or some sort of property or check, through which we can know exactly what type of data is in QR.

Additional context
Add any other context or screenshots about the feature request here.

@Priyank-Sharma-89 Priyank-Sharma-89 added the enhancement New feature or request label Jul 14, 2021
@Priyank-Sharma-89 Priyank-Sharma-89 changed the title [BUG] Know exact type/format[url/Contact/Phone/SMS/Text] of data provided by QR [FEATURE] Know exact type/format[url/Contact/Phone/SMS/Text] of data provided by QR Jul 14, 2021
@juliansteenbakker
Copy link
Collaborator

Please see #491 for a package that supports this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants