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(): articles need fields like in the section pages for sdi zones #529

Closed
wants to merge 1 commit into from

Conversation

bastianpahlke
Copy link

@bastianpahlke bastianpahlke commented Apr 17, 2024

Done in collaboration with @harryherbig

Sections already have an option to expose various fields, but articles do not so far. This pull request will change that.

@stroeer/buzz-end Please check this as it is my first approach on this repo

@bastianpahlke bastianpahlke changed the title BUZZ-3868: articles need fields like in the section pages for sdi zones feat(BUZZ-3868): articles need fields like in the section pages for sdi zones Apr 17, 2024
@bastianpahlke bastianpahlke changed the title feat(BUZZ-3868): articles need fields like in the section pages for sdi zones feat(): articles need fields like in the section pages for sdi zones Apr 17, 2024
Comment on lines +33 to +34
// meta information to render an article page such as commercial settings.
stroeer.page.section.v1.SectionPage.Section section = 5;
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks wrong to me. The equivalent of SectionPage.Section.fields is ArticlePage.Article.fields

Copy link
Contributor

Choose a reason for hiding this comment

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

that is true, and I also thought about just adding the fields, but since there are efforts to make ArticlePage and SectionPage models more similar, I preferred to use the whole Section field.
@bobaaaaa

Copy link
Contributor

@bobaaaaa bobaaaaa Apr 18, 2024

Choose a reason for hiding this comment

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

I know the issue. We need to deal with that in our FE too. I created an interface around ArticlePage and SectionPage for that reason.

Still: this change is wrong to me because of duplicate data. E.g. ArticlePage.article.section_tree & ArticlePage.section.section_tree

Copy link
Author

Choose a reason for hiding this comment

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

To quote Imogen Heap: "Where do we go from here":
So just the fields than or is something wrong with that too? Since we want to keep sections and articles more alike.

@bastianpahlke bastianpahlke deleted the BUZZ-3868 branch April 19, 2024 10:01
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.

3 participants