After reading over the code, I can't help thing kemal-session could be significantly simplified by just saving a single object. That is to say, removing all the strings, int32, int64, floats, bools etc.
You could tell users they had to define a storable object. They could then define the structure of the data they want to save. I typically want to save a user, so as long as my user has a to_json method (which is probable if I run an endpoint on it) I can the just nest in as a sub object.
ie
class SessionSchema
def initialize
end
JSON.mapping({
user: {type: User, nilable: true},
basket: {type: Basket, nilable: true},
flash:{type:String, nilable: true},
})
include Session::StorableObject
endThis would remove many of the current macros and possibly make it easier for developers to add other store engines.
What do you think?
After reading over the code, I can't help thing kemal-session could be significantly simplified by just saving a single object. That is to say, removing all the strings, int32, int64, floats, bools etc.
You could tell users they had to define a storable object. They could then define the structure of the data they want to save. I typically want to save a user, so as long as my user has a to_json method (which is probable if I run an endpoint on it) I can the just nest in as a sub object.
ie
This would remove many of the current macros and possibly make it easier for developers to add other store engines.
What do you think?