-
Notifications
You must be signed in to change notification settings - Fork 21
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
Table Shape Model #13
Comments
Job #13 is now in scope, role is |
Bug was reported, see §29: +15 point(s) just awarded to @emilianodellacasa/z |
Job |
@emilianodellacasa are you sure we need a table's shape...? After all, tables will be just some square representations on the UI. Is it really wanted to represent them as round/square/hexagon or whatever shape the table may have? My opinion is that only the number of sits is important... |
@amihaiemil If you see in the image I pasted in the README, each Table may have its own shape so we have to keep this model |
@amihaiemil/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please. |
@amihaiemil The impediment for #13 was registered successfully by @amihaiemil/z |
@emilianodellacasa the puzzle #72 is still not solved. |
@emilianodellacasa can we close?:) |
@amihaiemil Of course, thanks a lot! |
@ypshenychka/z please review this job completed by @amihaiemil/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed |
The job #13 is now out of scope |
@0crat quality good |
Order was finished, quality is "good": +35 point(s) just awarded to @amihaiemil/z |
@emilianodellacasa the puzzle #162 is still not solved; solved: #72. |
The Table Shape model represents the shape a Table can have.
The main attributes are:
Table Shape should have its own management pages to list, create, edit and delete them. In the index page it should be possible to sort and filter for every column.
In this issue, a table_shape_id should be also added to Table model (developed in #12) and managed/viewed.
The text was updated successfully, but these errors were encountered: