Skip to content
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

📝 feat: update club models #911

Merged
merged 23 commits into from
Jun 5, 2024
Merged

📝 feat: update club models #911

merged 23 commits into from
Jun 5, 2024

Conversation

garrettladley
Copy link
Member

@garrettladley garrettladley commented May 25, 2024

  • club model update
  • poc -> leader
  • contact -> social
  • service vs transactions separation of concerns

prior to merge

  • test with postman
  • ensure all instances of 'poc' are gone
  • multiple application support through endpoints

@garrettladley garrettladley linked an issue May 25, 2024 that may be closed by this pull request
@garrettladley garrettladley requested review from a team and DOOduneye and removed request for a team May 25, 2024 19:46
Copy link
Contributor

@DOOduneye DOOduneye left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fantastic! I think my big comment is about extensibility. I think a club should have a many recruiting objects.

Each recruiting object is a certain set of people theyre recruiting like software engineers vs designers vs things that are external like clubs like generate have applications for clients but you're not becoming a member from it.

@@ -0,0 +1,180 @@
package leadership
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we're switching to leadership as a term, we should also remove the term "poc" so lID instead of pocID and etc


type CreatePointOfContactBody struct {
type CreateLeaderBody struct {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit but should this be leadership instead of leader? leader implies something different

Name string `json:"name" validate:"required,max=255"`
Email string `json:"email" validate:"required,email,max=255"`
Position string `json:"position" validate:"required,max=255"`
}

type UpdatePointOfContactBody struct {
type UpdateLeaderBody struct {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above and anytime the term leader is used over leadership

@garrettladley
Copy link
Member Author

@DOOduneye what i went with was Leadership is the plural of Leader

@garrettladley garrettladley merged commit 936f90d into main Jun 5, 2024
3 of 4 checks passed
@garrettladley garrettladley deleted the 804-update-clubs-model branch June 5, 2024 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update Clubs Model
2 participants