Skip to content

De-Couple EA from EaType #5

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

Open
Hobadee opened this issue Oct 16, 2024 · 0 comments
Open

De-Couple EA from EaType #5

Hobadee opened this issue Oct 16, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Hobadee
Copy link
Owner

Hobadee commented Oct 16, 2024

EAs are basically the same regardless of type. (computer, mobile, user) Right now the strategy/facade wants only a single type at a time, and treats them somewhat differently. The framework is there to handle them all as one giant EaList object, as each EA has it's type attached to it. We should beef up the strategies/facades to not particularly care about the type of EA at the beginning, and only when it encounters the individual EA object. This would make it simpler to sync all EAs from disk to Jamf, for example, as a single EaList object could be generated and passed to the Jamf strategy.

@Hobadee Hobadee added the enhancement New feature or request label Oct 16, 2024
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

1 participant