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

MOD-2833 : Add properties, events and method for TagTechnologyNfcV (ISO15693) #46

Open
wants to merge 4 commits into
base: NativeTagSupport
Choose a base branch
from

Conversation

anil-shukla-axway
Copy link
Contributor

@anil-shukla-axway
Copy link
Contributor Author

@fasihul-axway Please review this PR.

@build
Copy link

build commented Mar 8, 2021

Messages
📖

✅ All tests are passing
Nice one! All 89 tests are passing.

📖

💾 Here are the artifacts produced:

Generated by 🚫 dangerJS against 423d58b

Copy link

@fasihul-haque fasihul-haque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anil-shukla-axway, please add api documentation, i do not see any YML document with this PR.

Copy link

@fasihul-haque fasihul-haque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anil-shukla-axway, please see my comment, i think some code refinement required before merging this PR. Once you done with changes, please update YML accordingly.

ios/Classes/TiNfcVTagTechnology.m Outdated Show resolved Hide resolved
ios/Classes/TiNfcVTagTechnology.m Outdated Show resolved Hide resolved
ios/Classes/TiNfcVTagTechnology.m Outdated Show resolved Hide resolved
ios/Classes/TiNfcVTagTechnology.m Show resolved Hide resolved
uint8_t requestFlags = [requestFlagsValue unsignedCharValue];

[[self.tagProxy asNFCISO15693Tag] getMultipleBlockSecurityStatusWithRequestFlag:requestFlags
blockRange:NSMakeRange(0, 8)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why using hardcoded blockRange? As per apple documentation range should be "The range of blocks. Valid start index range is 0 to 255 inclusively. Valid length is 1 to 256 inclusively."

ios/Classes/TiNfcVTagTechnology.m Outdated Show resolved Hide resolved
ios/Classes/TiNfcVTagTechnology.m Outdated Show resolved Hide resolved
ios/Classes/TiNfcVTagTechnology.m Outdated Show resolved Hide resolved
ios/Classes/TiNfcVTagTechnology.m Outdated Show resolved Hide resolved
ios/Classes/TiNfcVTagTechnology.m Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants