mirror of
https://github.com/gradio-app/gradio.git
synced 2025-04-12 12:40:29 +08:00
* Allow setting alpha * Allow setting beta and radius * Formatting * Change to tuple of (alpha, beta, radius) * Renamed parameter * Formatting * add changeset * add to update * Change to tuple of (alpha, beta, radius) * Renamed parameter * Formatting * Docstring for Model3D * rename parameter * add changeset * type * 180 * dupe * 180 * linting * lint * lint * add test * Formatting in docstring + added what unit the angles are * Added babylon types to model3d's package.json * pnpm lockfile * Type narrowing of helperCamera + assumed not null * refactor * docstring * lint * type checking * fix test --------- Co-authored-by: Mehdi <mehdi.bahri@epicgames.com> Co-authored-by: gradio-pr-bot <gradio-pr-bot@users.noreply.github.com> Co-authored-by: Abubakar Abid <abubakar@huggingface.co>
Backend Testing Guidelines
- All the tests should test Backend functionalities. Frontend functionalities and e2e tests are done in Frontend.
- Make use of pytest fixtures whenever it is possible. With fixtures, objects with high initialize durations are reused within tests, ex. a client session.
- All testdata resides within _gradio/test_data and all test_files resides within test/test_files.
- When doing network operations do not forget to make use of async to make tests faster.
- Have clear class and function naming within the tests.
- Short descriptions within test functions are great.
- Library function docstrings is expected to contain an example, please add missing docstrings to the library while you are writing tests the related function.
- Library docstring examples and descriptions are expected to align with tests, please fix divergent tests and library docstrings.