alamid
alamid copied to clipboard
peerigon
Framework for RESTful JavaScript web applications that run both on the server- and clientside.
There should be a `.setNode()` like a `.getNode()` as `_nodes`-property should be treated as _protected_/_private_ and there are cases in which you want add a manually a node to `_nodes`.
## writeables There are attributes which only make sense on client OR server. Those attributes should not be send over the wire on save/update calls. Sending them might cause the...
A validator request should take the same path as a service request and apply all schema-setters and middleware the service applies. If you've got a service request with some middleware...
There are situations where REST seems odd or is not fully applicable like reset password. A reset password request doesn't modify the user instantly, but triggers usually an email with...
alamid is currently hiding casting errors. If there is an inconsistent date or a float where a number is expected alamid sets `null` and does nothing. Thus bugs (like the...
We need to find out which Classes are basically a Singleton in alamid. These classes should provide a getInstance()-method like the `Bundler.class`. Currently it looks like these classes should be...
Alamid currently hides page.js for the developer behind the Client.class. This is not useful since routing is still an issue when it comes to support legacy browsers like
It should be possible to omit the method when calling `Server.addRoute()`. In this case all methods are applied.
The model code is potentially buggy and partially inefficient. - I think we should move some parts into an own class (e.g all the stuff related to `set`, `get`, `validate`)....
Calling client.dispatchRoute() on client.start() doesn't change the path in the location bar.