Update examples

[creator-woow]

Think it's pretty example

https://github.com/creator-woow/yoldi-profiles

[netlify]

👷 Deploy request for pr-fsd pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	e071ae7

[illright]

I noticed that there are errors when I run Steiger, the FSD linter, on this project. Could you fix them please?

[creator-woow]

@illright Yeah I see, I'm gonna fix it

[creator-woow]

@illright Fixed. Only 4 left, the reason is I can't name pages folder according fsd while using nextjs 14+, so linter doesn't check my pages folder (pages-view in my case). As soon as builder sees pages folder it starts build like I use pages router (while I'm using app router)

[illright]

What about this solution? https://feature-sliced.design/docs/guides/tech/with-nextjs#moving-the-pages-folder-of-nextjs-to-the-root-folder-of-the-project-recommended

[creator-woow]

@illright The solution is for pages router, I use latest app router, so it's not fit

[creator-woow]

@illright Below was my case solution (https://feature-sliced.design/docs/guides/tech/with-nextjs#app-router). I fixed all except these two. The reason is that they referenced only once, but while app scaling amount on their references will be enough, so I don't thing these are problem

[illright]

These errors point to unnecessary slices. Your app looks quite simple, so it doesn't really need the layer of features (and possibly, doesn't even need entities). Consider trying to fit the app in just Shared, Pages, and App, the architecture will be simpler.

[creator-woow]

@illright If I remove unnecessary slices, will you merge the request?

[illright]

These slices are indeed a blocker, but I may have some more comments after this refactor

[creator-woow]

@illright Okay, no staiger errors had stayed

[creator-woow]

@illright Pls either review & merge, or close pr, if you won't merge it

[illright]

I will review it when I get through other higher-priority things and find the time. I'm intending to merge this PR, so I don't want to close it, but I can't give an estimate for when I can do the review.

If you'd like to speed up the process of getting this PR merged, I can suggest asking someone in our Telegram chat for review. Perhaps they could point out some improvements and you could implement them ahead of the final review

[creator-woow]

I will review it when I get through other higher-priority things and find the time. I'm intending to merge this PR, so I don't want to close it, but I can't give an estimate for when I can do the review.

If you'd like to speed up the process of getting this PR merged, I can suggest asking someone in our Telegram chat for review. Perhaps they could point out some improvements and you could implement them ahead of the final review

Got it, thank you for fast reply