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

Add Forum settings to Channel struct #1306

Merged
merged 12 commits into from
Jan 3, 2023
Merged

Add Forum settings to Channel struct #1306

merged 12 commits into from
Jan 3, 2023

Conversation

@FedorLap2006 FedorLap2006 added this to the v0.27.0 milestone Dec 25, 2022
Copy link
Collaborator

@FedorLap2006 FedorLap2006 left a comment

Choose a reason for hiding this comment

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

Thank you for the PR! Here's some of my thoughts on it:

  • We usually prefix the constant values of various types, to allow for better discoverability.
  • Channel structure is only used for retrieving data from the API. The fields might also need to be added into ChannelEdit structure, to allow for usage in Modify endpoint. They should have omitempty, and if necessary, pointer type. If a field has a possible null value, just leave a "nullable" TODO, and keep it a pointer.

structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
@FedorLap2006
Copy link
Collaborator

FedorLap2006 commented Dec 31, 2022

Sorry for reviewing it at such a time. Kinda forgot about the PR in all the holiday stuff.
Anyhow, happy new year!

Co-authored-by: Fedor Lapshin <fe.lap.prog@gmail.com>
@ikafly144
Copy link
Contributor Author

In my area, the New Year has come a little earlier.
It's still early but Happy New Year!

@FedorLap2006
Copy link
Collaborator

Thank you for a quick response, I'll probably merge the PR on the week.

structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
structs.go Outdated Show resolved Hide resolved
@FedorLap2006 FedorLap2006 merged commit ae8894b into bwmarrin:master Jan 3, 2023
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.

2 participants