Created ChapterDetails Component

[Rajgupta36]

Resolves #474

Tasks:

• Create ChapterDetails Component
• Add Test Cases for ChapterDetails
• Add Missing Test Cases for ProjectDetails
• Fix Minor Issues

---

Media

[kasya]

Thanks for working on this. Some comments ⬇️

[kasya]

@Rajgupta36 sorry it took me a moment to get back to this one! Could you resolve conflicts? I'll review it as soon as that's ready to view!

[arkid15r]

It seems we need to be smarter here in a long-term perspective. How about creating a generic entity details page component (like the Card we have for projects/chapters/committees) that could be reused for any entity depending on the fields passed to the function. So here and for committee details page too we'd just use the same code.

@Rajgupta36 does it make sense?

[Rajgupta36]

It seems we need to be smarter here in a long-term perspective. How about creating a generic entity details page component (like the Card we have for projects/chapters/committees) that could be reused for any entity depending on the fields passed to the function. So here and for committee details page too we'd just use the same code.

We could use a generic component, but putting all logic into a single file might make things more complex. Would it be better to make it modular? Perhaps we can use two generic components and handle some features like the map (ChapterPage) and issues/releases (ProjectPage) in their respective pages. What do you think, @arkid15r and @kasya ?

[Rajgupta36]

Should I do this in this PR, @arkid15r?

[arkid15r]

Should I do this in this PR, @arkid15r?

Up to you, we can merge this one but it'll require more refactoring then.
Sorry I haven't suggested this approach earlier.

[Rajgupta36]

Should I do this in this PR, @arkid15r?

Up to you, we can merge this one but it'll require more refactoring then. Sorry I haven't suggested this approach earlier.

Okay, I completed this in a few minutes and created an issue (like the test cases earlier).

[Rajgupta36]

Also, @arkid15r, what about these issues: #536, #549, #550, #551 ? I think the refactor depends on these issues.

[Rajgupta36]

@kasya It’s ready for review.

[arkid15r]

Also, @arkid15r, what about these issues: #536, #549, #550, #551 ? I think the refactor depends on these issues.

The only one with map seems significant. And other don't look like they being taken care of.

[arkid15r]

I'm going to merge it as is -- we're going to unify it from the code reuse perspective.

Thanks for adding this @Rajgupta36!