Positions API #7
No reviewers
Labels
No Label
priority
high
priority
low
priority
medium
priority
very high
BUG
Feature
High Priority
Low Priority
Medium Priority
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: public/pyceo#7
Loading…
Reference in New Issue
No description provided.
Delete Branch "positions-api"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Haven't got tests working yet, but the main codes should be there.
1a9d4755cb
to0ed876c010
Positions APIto WIP: Positions API@r345liu Excellent work. Just a few minor adjustments. And, of course, unit tests.
WIP: Positions APIto Positions API@ -29,3 +29,2 @@
return False
if section.startswith('auxiliary '):
return val.split(',')
if section.startswith('auxiliary ') or section == 'positions':
What is the difference between auxiliary and non-auxiliary configs? Because if we use "auxiliary positions" as the section key then a special case wouldn't be needed here.
Anything 'auxiliary' is supposed to be 'supplementary'. For example, 'auxiliary groups' are the supplementary groups to which a user should be added when they are added to a main group.
Unfortunately INI files don't allow us to specify data types, and we can't use a comma as a general-case delimiter since the LDAP bases contain commas. So we'll just have to check the name of the section on a case-by-case basis.