feat: add spibridgedatatype to bios information #1005
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adds spibirdgedatatype information to bios in order to be able to know security chip information from older MacOS devices
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
I'm currently using systeminformation to get information in Ubuntu, MacOS and Windows devices and I'm loving it. Nonetheless I need to get more information about BIOS in MacOS devices, specifically security chip in older MacOS devices. I was thinking of just calling it from my code, but I think it's better if we extend systeminformation to get it.
I opted for using:
system_profiler SPiBridgeDataType -jsonafter the execution of the code to get
SPHardwareDataTypein Darwin and following the type of coding I saw in the original file. That adds to theresultobject if everthing went well and then it should resolve itself or call the callback function (if callback is a function really haha).Let me know if everything seems to be fine and if this helps you in any way. I would be glad if you can add this to the next release :)!