Feature/change app structure

[jesperengstrom]

Description

Solves

Made an attempt at re-structuring the app (or really, reverting it to how it once was), mainly since (find)/+layout.server.ts has grown a bit out of hand and the search result really feels like it should be a component rather than a layout template. Also tried to gather the types and utils that were placed all over.

With this approach, we can begin to optimize the data fetching for the resource page, without worrying about breaking things on the /find route for example. The types that got lost in the resource load function are now back etc etc.

(On the downside, the load functions now have some duplicate logic. If this feels like a problem, we could maybe delegate it to an internal /find api route?)

Before:

(app)
   [[lang=lang]]
      (find)
         +layout.server.ts <-- data fetching
         +layout.svelte <-- search result
         find
            +page.svelte <-- basically nothing
         [[fnurgel=fnurgel]]
            +page.svelte <-- slot content

After:

(app)
   [[lang=lang]]
      find
         +page.server.ts <-- data fetching
         +page.svelte
            <SearchResult/>
      [[fnurgel=fnurgel]]
         +page.server.ts <-- data fetching
         +page.svelte
            <Stuff/>
            <SearchResult/>

Summary of changes

• Change file structure, move files, fix imports.
• Breakout <SearchResult> component
• Move all types to $lib/types/[name].types.ts
• Move some utils to $lib/utils
• Remove some duplicate utils
• Fix unit tests

[johanbissemattsson]

Awesome work restructuring the load functions and fixing the types (and gathering all types in the $lib folder)! ⭐

It would be preferable to merge this soon to minimize the need to resolve merge conflicts (we’re currently working on relatively few simultaneous changes in the code base so it would fit very good timewise).

[olovy]

LGTM! 🚢