Integrate Server Actions into Pages to Fetch Data #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to allow pages to fetch data through server actions. The key changes involves refactoring numerous pages into separate async components that handles server-side logic, allowing the application to support dynamic server-side data.
Server Action Integration:
[Category]Data.tsx
naming format; the component themselves are wrapped by CategoryPost.tsx, which renders a fallback component while fetching data to enhance user experience.lang
of type"en" | "tr"
, to indicate whether the page should render inEN
orTR
. Only hardcoded labels, such asComments
, will be affected by this parameter; the data fetched will not takelang
into consideration.Code Readability Improvements:
(category)/(en)
and(category)/(tr)
for easier readability, with the help of NextJS's documentation on Route Groups. These changes will not affect URL pathing.Back to Home
link due to refactored components, when users are browsing in eitherEN
orTR
languages.text
parameter of type String to maintain readability, while cleaning up repeated sections:Minor Schema Fix:
memberSize
property has been changed fromnumber
tostring
to correctly parse its expected type"low" | "mid" | "high"
[category].model.ts
: The default exports have been tweaked to resolve an issue, where Mongoose throws outOverwriteModelError: Cannot overwrite 'Model' model once compiled.
when a schema is already defined.This closes issue #14