-
Notifications
You must be signed in to change notification settings - Fork 0
Roadmap
Development roadmap for Spot v1.0
- Would ship with all the basics (string, integer, boolean, etc.)
- Users could register their own types like “json” or “encrypted_string”
- Registered types would handle:
- Basic type validations and error messages (integer is numbers only, etc.)
- Casting (integer, string, boolean)
- Setting values (encrypting, casting, serializing before inserting, etc.)
- Getting values (decrypting, casting, deserializing after retrieving, etc.)
[None of this is currently extensible in Spot right now - it’s built in and inflexible]
Users should be able to add multiple validations to specific fields, combine them, use callbacks for conditional validations dependent on other fields being set, customize the validation error messages, etc.
[Right now the only validation built into spot is a “required” check and it is not easily changeable or extensible]
This can be done transparently and automatically with relations with a little work that I so far have not had time for. Basically when a user does something like $post->comments, ALL the comments for ALL the posts in the current collection would be loaded in one query using an IN() clause, and then hydrated into objects and loaded back onto each $post object in their own collections. This means a loop of posts with $post->comments would be at most 2 queries instead of N+1.