-
Notifications
You must be signed in to change notification settings - Fork 248
WIP: Initial POC for split user interface and new API #832
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While here do some bugfixes to get PoC running
Since they are optional remove them completely
For validation and error handling of incoming JSON data it is required to have type and immuble features listed in models.
NULL fields are in this context considered optional fields
Alternative route of using getPrimaryKey() also seems do-able, how-ever like to stick with all column features concetrated.
Primary key is generated as auto-increment value
JSON keys do not always represent the db_column value
I keep forgetting commands when swtiching betwen development machines.
Quite usefull since expansion parametesr can be freely set ,e.g. they are not linked to a class (yet), how-ever without implementation in shared.inc.php they do not expand.
Also check for assignment errors and ensure validation requires like code within case statements.
Assert should check for one object which is returned
While here re-wrote joinQuery, since the abstraction used was highly confusing and un-readable.
NotifcationUtils expect an Login instance set, which is not used within APIv2.
Member
Author
|
Moved to #845 change from @rickvanderzwet namespace to hashtopolis namespace. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #814 for bit of background info on this. This is a new approach for the development using Slim Framework instead of Restler.