#298-update-delete-middleware #349
No reviewers
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!349
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "#298-update-delete-middleware"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Modified the middleware to be able to update and delete in the database
Review:
Code appears to follow established coding standards, new methods are have good documentation. However there is a lack of descriptive comments that explains what different sections of code are actually doing.
Main() is completely devoid of comments.
Built and test-ran application, all current app pages displaying as expected. Currently no way to test update and deletion methods, suggest creation of unit tests for the new methods.
Additional recommendations:
will try to fix everything, would appreciate if someone knew how to do the update, could not find how to update the whole row(without complex sql query)
With the current "payload" i do not believe it is even possible to do it, without a complex sql query, since we are cramming an entire row into a single string. In fact I believe that is part of the problem that issue #19 is intended to solve.
then i think it would be best to merg this as it is and then we could work on that on this version, i may even take on issue #19 because i have worked some with how middleware works.
I have been talking to the developer and we have decided that this pull request will spawn some new issues related to the reviewers feedback. The review has been conducted in a good fashion, this will be merged directly.