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

Add OS Version to Deprecations & Output Issues via Text or Other File Formats #21

Open
uurazzle opened this issue Oct 26, 2023 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@uurazzle
Copy link

💡Add OS Version to Deprecations

Would be nice to a specific versions of OS that the deprecations for payloads are noted.

Also, would be nice to be able to export out as text or "share sheet functionality" issues to make it easier to distribute it via other mechanisms.

✅ Proposed solution

Add details for operating systems that the deprecation applies when listing payload is deprecated.

🩹 Alternatives Solutions + Workarounds

Research it yourself outside application.

ℹ️ Additional context

For example on "Deprecation" icon, could add OS version its deprecated to bottom image, etc.
image

For example, would be nice to have an export as text, or some other file format or use share sheet via OS?
image

@uurazzle uurazzle added the enhancement New feature or request label Oct 26, 2023
@ninxsoft ninxsoft added the help wanted Extra attention is needed label Oct 28, 2023
@ninxsoft
Copy link
Owner

Low Profile relies on the Profile-Specific Payload Keys metadata, which currently does not provide OS versions for when keys are deprecated. For example, the Parental Controls (Game Center) payload properties metadata is sourced from here: ParentalControlsGameCenter

Apple does, however, provide this metadata in the Device Management Client Schema project. For example: com.apple.gamed.yaml

Low Profile relies on Yams for YAML parsing, which currently does not support circular references that exist in the schema. Until jpsim/Yams#274 is fixed, or until I find a clever way around the circular references, Low Profile may just have to wait for this feature to be implemented 🙏

Regarding the exporting of issues, Low Profile does support exporting a full report to a .lowprofile file (which can be opened on another Mac). What was the specific use-case you had in mind regarding the export of issues?

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

No branches or pull requests

2 participants