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

Addressing issues related to #613 #677

Merged
merged 7 commits into from
Apr 10, 2024
Merged

Addressing issues related to #613 #677

merged 7 commits into from
Apr 10, 2024

Conversation

tchx84
Copy link
Owner

@tchx84 tchx84 commented Apr 5, 2024

Fixes #613

@tchx84 tchx84 marked this pull request as draft April 5, 2024 19:00
tchx84 added 7 commits April 8, 2024 10:44
Before this change, to determine the appropriate permission model
for a given group+key+option tuple, it would iterate over each of
the models each time.

With this change that's no longer needed. Plus, it's now possible
to  apply  different  treatments in  cases where the  model don't
parse the value in the same way as the oher models,  e.g., envars
overrides.

Issue #613
@tchx84 tchx84 marked this pull request as ready for review April 8, 2024 15:02
@tchx84 tchx84 merged commit 0aa8957 into master Apr 10, 2024
1 check passed
@tchx84 tchx84 deleted the issue-613 branch April 10, 2024 18:06
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.

Issue displaying values with semicolon
1 participant