> For the complete documentation index, see [llms.txt](https://docs.17movement.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.17movement.net/phone/building-custom-apps/auth/defining-global-types.md). # DEFINING GLOBAL TYPES To ensure Type Safety throughout the application and allow the [**TypeScript**](https://www.typescriptlang.org/) compiler to recognize the new global authentication functions (such as `handleLogin` and `handleRegister`), we must extend the global type declarations. ### Implementation Open the file `web/src/types.d.ts` and add the following type declarations starting from `handleLogin` down to `useSignOut`. These definitions inform **TypeScript** about the existence, arguments, and return types of these functions, preventing compilation errors in the views and hooks. {% code overflow="wrap" lineNumbers="true" %} ```typescript declare function handleLogin( username: string, password: string ): Promise<{ success: boolean; message: string; }>; declare function handleRegister( username: string, password: string, accountData: unknown, ): Promise<{ success: boolean; message: string; }>; declare function useCurrentUser(): { username: string; accountData: unknown } | null; declare function useIsAuthenticated(): boolean; declare function useSignOut(): void; ``` {% endcode %} {% hint style="info" %} ***Note**: The existing utility declarations (e.g., `openGalleryPicker`, `startCall`, `useSettings`, etc.) already present in `types.d.ts` should remain untouched. You only need to append the new authentication declarations listed above.* {% endhint %} ### Functions Reference #### `handleLogin` ```typescript const response = await handleLogin( 'username', 'password' ); console.log(response); ``` **Arguments**

Name	Type	Optional	Description
`username`	string	❌	The username to attempt login with.
`password`	string	❌	The user's password.

**Returns**

Name	Type	Description
`success`	boolean	The `success` boolean is `true` upon success.
`message`	string	The `message` string provides an error description (if unsuccessful) or a confirmation message.

#### `handleRegister` **Example** ```typescript const response = await handleRegister( 'newuser', 'securepassword', { email: 'test@example.com', age: 30 } ); console.log(response); ``` **Arguments**

Name	Type	Optional	Description
`username`	string	❌	The username for the new registration.
`password`	string	❌	The new user's password.
`accountData`	unknown	✅	Optional additional account data to be saved (e.g., email, date of birth). Can be `null`.

**Returns**

Name	Type	Description
`success`	boolean	The `success` boolean is `true` upon success.
`message`	string	The `message` string provides an error description (if unsuccessful) or a confirmation message.

#### `useCurrentUser` **Example** ```typescript const user = useCurrentUser(); if (user) { console.log(`Logged in as: ${user.username}`); } ``` **Returns**

Name	Type	Description
`username`	string	Current login username
`accountData`	unknown	Return data provided while registering

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.17movement.net/phone/building-custom-apps/auth/defining-global-types.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.