-
-
Notifications
You must be signed in to change notification settings - Fork 357
Add category to Chapters Table schema #71
Comments
Hi @allella, do we have a PR renaming the table "groups" to "chapters"? Also, I think we should update the terminology on docs. |
@rodmsmendes that’s why I opened this issue. I did not see that in modifications of the sql or documentation file, I’m glad your check agrees with mine. |
@nik-john @francocorreasosa are you guys able to answer / resolve this one in the course of #46? |
@nik-john @allella @xarielx I think the PR #46 should be merged asap. I mean, that's a first step towards the API implementation and naturally, it will raise a lot of questions and suggestions. But if we keep modifying the PR #46 it will require more revision, and we will be stuck in a loop. So, my opinion is that we should not modify the PR anymore, merge it and then create new issues. |
@nik-john Understood, on it. |
#46 was merged, so I suspect someone can create a PR for this now. I'm helping more with docs and cat herding, so I'll defer to someone more familiar with the stack. |
fix/feat/api/swagger.json fix/feat/data/ddl.sql Added category label of types tring to the schemas closes #71
This will make it easier for a user to filter the chapters by interests, i.e. sports, events. Since the current schema has description and details, a more general “category” will make it easier to find the right chapter. If the chapter wants to be a private one, a private option will be added and won’t be able to be found by filtering by category.
Solution: Add category to existing chapter table schema.
The text was updated successfully, but these errors were encountered: