AllDotPy/FletX

AI Summary: The FletX "Routing System" documentation is currently too dense and abstract for new users. The goal is to simplify it by introducing concepts step-by-step, providing a clear overview of its purpose and how it builds on Flet's native navigation, and incorporating practical, example-driven explanations for route mapping and page navigation.

AI Summary: This GitHub issue proposes simplifying the integration of common navigation widgets (like `AppBar`, `NavigationDrawer`, `BottomNavigationBar`) into `FletXPage` classes. The current method requires boilerplate code, and the suggestion is to add direct parameters to the `FletXPage` constructor, making development faster and cleaner.

AI Summary: The task is to debug and fix a `RuntimeWarning` in the FletX Python framework. The warning, 'coroutine 'FletXApp._execute_hooks' was never awaited', occurs when using an asynchronous shutdown hook. The solution involves ensuring that the `_execute_hooks` coroutine is properly awaited within the `app.run()` method's shutdown logic to correctly execute asynchronous shutdown functions.

AI Summary: Implement a `fletx test` command in the FletX CLI, leveraging pytest for running unit and integration tests. This involves updating the CLI entrypoint, creating a test runner utility, and documenting the new command. The command should support various pytest arguments like `-k`, `-v`, `--coverage`, and `--pdb` for flexibility and debugging.

AI Summary: Implement comprehensive unit tests for the core reactivity components of the FletX framework (ReactiveDependencyTracker, Observer, Reactive, Computed, and Rx[T] variants), covering initialization, dependency tracking, change propagation, and computed value updates.

AI Summary: The task is to fix a bug in the FletX Python framework where the `on_shutdown` hooks are executed prematurely during initialization instead of during application closure. The solution involves re-wiring the `on_shutdown` hooks to the `ft.Page.on_close` event to ensure they are called at the correct time.

AI Summary: Write unit tests for the HTTPClient class in the FletX Python framework using pytest. This involves creating a new test file (`tests/test_httpclient.py`) and writing tests to cover various aspects of the HTTPClient's functionality, such as successful requests, handling errors, and potentially different HTTP methods.

AI Summary: Implement a default 404 page component in the FletX routing system to handle unmatched routes gracefully. This component should be displayed automatically unless a custom 404 page is explicitly defined by the user.

AI Summary: Create unit tests for the FletXApp class in a new file, `tests/test_fletxapp.py`, using the pytest framework. The tests should cover basic functionality of the FletXApp class, as defined in the FletX project.