Releases: oedotme/generouted
v1.15.3
Commits
- fix: normalize all plugins listeners pages path fd1d55d by @oedotme
- fix: normalize path for windows (#108) 83951cc by @agustinbravop
- docs: reference main docs from integrations readme 99e46df by @oedotme
- chore: update prettier config f24dd0a by @oedotme
Changelog: v1.15.2...v1.15.3
Contributors
Assets 2
v1.15.2
Commits
- fix: prettier bin path resolving on windows 9644c96 by @oedotme closes #105
- feat: exclude layout groups from modal path 86355ff by @oedotme
- chore: update packages 53a67db by @oedotme
- docs: update custom integration examples links ea4df3a by @oedotme
- chore: update custom integration examples 378ab9a by @oedotme
Changelog: v1.15.1...v1.15.2
Contributors
Assets 2
v1.15.1
Commits
- feat: update tanstack router plugin and example with latest changes (#100) 9be6274 by @AkshayPathak
Changelog: v1.15.0...v1.15.1
Contributors
Assets 2
v1.15.0
Changes
Introduce route-based and app-level Pending component as a Suspense fallback for both @generouted/react-router and @generouted/solid-router
export const Pending = () => <div>Loading...</div>Breaking change 🚨
For @generouted/solid-router, now the routes tree/object has the src/pages/_app.tsx as the root route and all the routes render as children like the current implement for @generouted/react-router.
You need to make two changes only at src/pages/_app.tsx for this new update:
- Render an
<Outlet />component from@solidjs/routerinstead of{props.children} - Render the
<Modals />component explicitly, it was included previously at the exported<Routes />component
// src/pages/_app.tsx
import { Outlet } from '@solidjs/router'
import { Modals } from '@generouted/solid-router'
import { useModals } from '../router'
export default function App() {
const modals = useModals()
return (
<section>
<header>
<nav>...</nav>
<button onClick={() => modals.open('/login')}>Open modal</button>
</header>
<main>
<Outlet />
</main>
<Modals />
</section>
)
}Commits
Changelog: v1.14.0...v1.15.0
Contributors
Assets 2
v1.14.0
Changes
You can now export an app level error boundary Catch component from src/pages/_app.tsx with the following integrations:
@generouted/react-router,@generouted/react-router/lazy
// src/pages/_app.tsx
export const Catch = () => <div>...</div>@generouted/solid-router,@generouted/solid-router/lazy
// src/pages/_app.tsx
export const Catch = (props: { error: Error; reset: () => void }) => <div>...</div>Breaking changes 🚨
If you're using the generatePreservedRoutes directly from the core functions or through a custom integration you should now access the default export explicitly:
const preservedRoutes = generatePreservedRoutes(PRESERVED)
-const App = preservedRoutes?.['_app'] || Outlet
-const NotFound = preservedRoutes?.['404'] || Fragment
+const App = preservedRoutes?.['_app']?.default || Outlet
+const NotFound = preservedRoutes?.['404']?.default || FragmentCommits
Changelog: v1.13.7...v1.14.0
Contributors
Assets 2
v1.13.7
Changes
- Setup issue template
- Updated docs structure, content and conventions example
- Add file-based
Catchcomponent with error boundary for Solid integrations
export const Catch = (props: { error: Error; reset: () => void }) => <div>...</div>Commits
- chore: update packages d85724d by @oedotme
- docs: remove src/pages from conventions example table b374b0f by @oedotme
- docs: update logo size 19d01aa by @oedotme
- docs: move experimental and deprecated integrations to the bottom 8c034ff by @oedotme
- docs: update readme structure and content e6e9d07 by @oedotme
- feat: add catch component w/ error boundary for solid-router a1758bb by @oedotme
- docs: add simple custom react-router example 5c88344 by @oedotme
- docs: update react-router custom example path 2b55dc2 by @oedotme
- chore: setup issue template 6b31a97 by @oedotme
Changelog: v1.13.6...v1.13.7
Contributors
Assets 2
v1.13.6
Commits
Changelog: v1.13.5...v1.13.6
Contributors
Assets 2
v1.13.5
v1.13.4
Commits
Changelog: v1.13.3...v1.13.4
