feat!: Replace implicitMode with defaultHash (#110)

BREAKING CHANGE

Author: webJose

AGENTS.md

@@ -9,8 +9,9 @@ The @svelte-router/core routing library supports simultaneous path and hash rout
 - **Path Routing** (`hash: false`): Uses URL pathname
 - **Single Hash Routing** (`hash: true`): Uses URL hash as a single path (e.g., `#/path/to/route`)
 - **Multi Hash Routing** (`hash: 'p1'`): Uses semicolon-separated hash segments (e.g., `#p1=/path;p2=/other`)
-- **Implicit Path Routing** (`hash: undefined`, `implicitMode: 'path'`): Resolves to path routing
-- **Implicit Hash Routing** (`hash: undefined`, `implicitMode: 'hash'`): Resolves to hash routing
+- **Implicit Path Routing** (`hash: undefined`, `defaultHash: false`): Resolves to path routing
+- **Implicit Hash Routing** (`hash: undefined`, `defaultHash: true`): Resolves to hash routing
+- **Implicit Named Hash Routing** (`hash: undefined`, `defaultHash: <a string>`):  Resolves to named (multi) hash routing
 
 #### Example Multi-Universe Setup
 ```svelte
@@ -268,7 +269,7 @@ ROUTING_UNIVERSES.forEach((ru) => {
         let cleanup: () => void;
         beforeAll(() => {
             cleanup = init({ 
-                implicitMode: ru.implicitMode,
+                defaultHash: ru.defaultHash,
                 hashMode: ru.hashMode
             });
         });
@@ -414,7 +415,7 @@ function bindablePropertyTests(setup: ReturnType<typeof createRouterTestSetup>,
         });
 
         // Trigger binding based on routing mode
-        const shouldUseHash = (ru.implicitMode === 'hash') || (hash === true) || (typeof hash === 'string');
+        const shouldUseHash = (ru.defaultHash === true) || (hash === true) || (typeof hash === 'string');
         const url = shouldUseHash ? "http://example.com/#/test" : "http://example.com/test";
         location.url.href = url;
         await vi.waitFor(() => {});
@@ -579,7 +580,7 @@ test("Should bind route parameters correctly.", async () => {
     });
 
     // Navigate to matching route
-    const shouldUseHash = (ru.implicitMode === 'hash') || (hash === true) || (typeof hash === 'string');
+    const shouldUseHash = (ru.defaultHash === true) || (hash === true) || (typeof hash === 'string');
     location.url.href = shouldUseHash ? "http://example.com/#/user/42" : "http://example.com/user/42";
     await vi.waitFor(() => {});
 
@@ -816,7 +817,7 @@ ROUTING_UNIVERSES.forEach((universe) => {
 
         beforeAll(() => {
             cleanup = init({ 
-                implicitMode: universe.implicitMode,
+                defaultHash: universe.defaultHash,
                 hashMode: universe.hashMode
             });
             setup = createRouterTestSetup(universe.hash);

README.md

@@ -21,7 +21,7 @@
 
 + **Always-on path and hash routing**:  Simultaneous, independent and always-on routing modes.
 + **Multi hash routing**:  Doing micro-frontends?  Routing tabs or dialogs using the URL?  Have as many paths as needed.
-+ **Sveltekit support**: Add hash routing on top of Sveltekit's path routing Via 
++ **Sveltekit support**: Add hash routing on top of Sveltekit's path routing via 
 [@svelte-router/kit](https://github.com/WJSoftware/svelte-router-kit)
 + **Electron support**:  Works with Electron (all routing modes)
 + **Reactivity-based**:  All data is reactive, reducing the need for events and imperative programming.
@@ -43,7 +43,7 @@
 + `RouterEngine.routes`
 + `RouterEngine.routeStatus`
 
-All data is a Svelte signal.  Add routes dynamically or reactively, change route conditions on the fly, and more pieces 
+All data is a Svelte signal.  Add routes dynamically or reactively, change route conditions on the fly, add more pieces 
 of user interface on-demand, etc.  All works reactively.
 
 ### Two Library Modes
@@ -89,7 +89,7 @@ Default:
 init(); // Or use initFull() for full-mode.
 
 // Common case:  "I just need good, old-fashioned hash routing."
-init({ implicitMode: 'hash' });
+init({ defaultHash: true });
 ```
 
 #### Electron Variant
@@ -441,7 +441,7 @@ Additional `goTo()` options:
 1. **Use `<Link>` components** for user-triggered navigation
 2. **Use `navigate()`** for programmatic navigation within routing universes
 3. **Use `goTo()`** only for direct URL manipulation
-4. **Try to specify `hash`** in `navigate()` instead of relying on the implicit mode whenever possible
+4. **Try to specify `hash`** in `navigate()` instead of relying on the default hash whenever possible
 
 Just in case you are wondering:  This navigation logic is already there in `<Link>` components:
 
@@ -461,8 +461,7 @@ As seen, the value of the `href` property never changes.  It's always a path, re
 
 > **⚠️ Important:** Not setting the `hash` property is **not the same** as setting it to `false`.  When `hash` is 
 > `undefined`, either because the property is not specified at all, or its value is set to `undefined` explicitly, the 
-> value of the `implicitMode` library option, which is set when the library is initialized, will be used to resolve a 
-> `true` or `false` value.
+> value of the `defaultHash` library option, which is set when the library is initialized, will be used instead.
 >
 > This is true for all components that support the `hash` property.