refactor(services): avoid nested fetchers

If we use fetchPostsCount inside fetchAllPostsSlugs, we might have
problems to test fetchAllPostsSlugs failure. So it is better to let
the consumer pass the posts count as an argument. The same applies
to thematics and topics.

1 files changed, 3 insertions, 1 deletions

diff --git a/src/pages/article/[slug].tsx b/src/pages/article/[slug].tsx
index f228ff0..04ae617 100644
--- a/src/pages/article/[slug].tsx
+++ b/src/pages/article/[slug].tsx
@@ -26,6 +26,7 @@ import {
   fetchAllPostsSlugs,
   fetchCommentsList,
   fetchPost,
+  fetchPostsCount,
 } from '../../services/graphql';
 import styles from '../../styles/pages/article.module.scss';
 import type { Article, NextPageWithLayout, SingleComment } from '../../types';
@@ -333,7 +334,8 @@ export const getStaticProps: GetStaticProps<ArticlePageProps> = async ({
 };
 
 export const getStaticPaths: GetStaticPaths = async () => {
-  const slugs = await fetchAllPostsSlugs();
+  const postsCount = await fetchPostsCount();
+  const slugs = await fetchAllPostsSlugs(postsCount);
   const paths = slugs.map((slug) => {
     return { params: { slug } };
   });