tpope / ldaptic Goto Github PK

Step 1 is a simple criteria constructor:

limit(3).filter(ou: "People")

This could later be expanded to allow dispatching class methods off of criteria:

def self.people
  filter(ou: "People")
end
limit(3).people

Make it possible to entry subclass extensions in separate files and have them be automatically loaded alongside the namespace in Rails.

Different attributes have different comparison semantics (e.g., case sensitive vs case insensitive). The library should be aware of this so that it doesn't try to persist two equivalents to the same attribute (which would cause a server error).

Should just be a couple of includes.

This isn't as simple as it seems, as LDAP attributes are inherently multivalued, and Active Model assumes single values. Also, does anyone actually need validations above and beyond what the server provides?

The logic is basically there. The API needs to be fleshed out a bit.

Right now, you can assign an arbitrary collection of strings to objectClass, but the internals of Ldaptic assume you have only added or removed an auxiliary class. And if you remove an auxiliary class, the accessors for its attributes disappear immediately, making it trickier to clear out those fields.