mkdocstrings-typescript 0.0.0__tar.gz → 0.1.0__tar.gz

mkdocstrings_typescript-0.1.0/CHANGELOG.md

@@ -0,0 +1,47 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
+and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
+<!-- insertion marker -->
+## [0.1.0](https://github.com/mkdocstrings/typescript/releases/tag/0.1.0) - 2025-03-24
+
+<small>[Compare with 0.0.1](https://github.com/mkdocstrings/typescript/compare/0.0.1...0.1.0)</small>
+
+**The project gets released to everyone!**
+
+### Build
+
+- Depend on griffe-typedoc 0.1 ([7d09f9a](https://github.com/mkdocstrings/typescript/commit/7d09f9a380a844296739e7eaad3554095af0400a) by Timothée Mazzucotelli).
+- Require Python 3.10 minimum ([1e5c521](https://github.com/mkdocstrings/typescript/commit/1e5c52140635bbd32d03aeaf7da6badeedef29c8) by Timothée Mazzucotelli).
+- Depend on mkdocstrings 0.28.3 ([c5bf04e](https://github.com/mkdocstrings/typescript/commit/c5bf04e063f12a0cf94e8164af29b9b986acb887) by Timothée Mazzucotelli).
+
+### Features
+
+- Declare and use symbols for all kinds of objects ([a2392aa](https://github.com/mkdocstrings/typescript/commit/a2392aaa8db99b468d70b7280584b96eb12c7ad9) by Timothée Mazzucotelli).
+- Support specifying an object path ([9b32feb](https://github.com/mkdocstrings/typescript/commit/9b32febbe0ad880eae3117d631db481ff344d16f) by Timothée Mazzucotelli). [Issue-22](https://github.com/mkdocstrings/typescript/issues/22)
+- Pass symbol map to `markdown` method of objects, to allow generating autorefs ([3324c2a](https://github.com/mkdocstrings/typescript/commit/3324c2adc62be8e44106f89169822e360d64c35e) by Timothée Mazzucotelli). [Issue-5](https://github.com/mkdocstrings/typescript/issues/5)
+- Suffix templates with jinja extension, add templates for enum, enum member, class and constructor ([49fcd56](https://github.com/mkdocstrings/typescript/commit/49fcd566b6d4e74f2bd4681829181be69f8edd05) by Timothée Mazzucotelli). [Issue-3](https://github.com/mkdocstrings/typescript/issues/3), [Issue-4](https://github.com/mkdocstrings/typescript/issues/4)
+- Generate project with gh:mkdocstrings/handler-template Copier template ([79a9244](https://github.com/mkdocstrings/typescript/commit/79a924496d190642e58d127f8b29640c81041c3f) by Timothée Mazzucotelli).
+
+### Bug Fixes
+
+- Add templates for projects ([9648248](https://github.com/mkdocstrings/typescript/commit/9648248efac8d1b0ecccce6bdec5e7882eaabdc8) by Timothée Mazzucotelli).
+- Add templates for namespaces ([277af0f](https://github.com/mkdocstrings/typescript/commit/277af0f7deab48c1d492e8e109c25a978bb43434) by Timothée Mazzucotelli). [Issue-mkdocstrings/typescript#16](https://github.com/mkdocstrings/typescript/issues/16)
+- Add templates for accessors ([57405cb](https://github.com/mkdocstrings/typescript/commit/57405cba0a2652cf21acdb89865cee29fbfff0ca) by Timothée Mazzucotelli). [Issue-13](https://github.com/mkdocstrings/typescript/issues/13)
+- Collect project anyway, not just its children ([3895e88](https://github.com/mkdocstrings/typescript/commit/3895e8812a731d075e5fbba4c771ecaebaa6af65) by Timothée Mazzucotelli). [Issue-2](https://github.com/mkdocstrings/typescript/issues/2)
+
+### Code Refactoring
+
+- Import from top-level mkdocstrings module ([a16da56](https://github.com/mkdocstrings/typescript/commit/a16da568a1d0cbd3d3099b62569211086a071313) by Timothée Mazzucotelli).
+- Improve support for signatures rendering (wip) ([bcbc314](https://github.com/mkdocstrings/typescript/commit/bcbc314203c6b9da24ca46a3db1536a61cffb3f3) by Timothée Mazzucotelli).
+
+## [0.0.1](https://github.com/mkdocstrings/typescript/releases/tag/0.0.1) - 2024-05-08
+
+<small>[Compare with first commit](https://github.com/mkdocstrings/typescript/compare/00cd6f133945a103d9e71cc6b413c0738a07f9d1...0.0.1)</small>
+
+### Build
+
+- Release no-op version ([04dfa30](https://github.com/mkdocstrings/typescript/commit/04dfa30942014a113806f9ad5981718a620a6532) by Timothée Mazzucotelli).

mkdocstrings_typescript-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at dev@pawamoy.fr. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+

mkdocstrings_typescript-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,120 @@
+# Contributing
+
+Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
+
+## Environment setup
+
+Nothing easier!
+
+Fork and clone the repository, then:
+
+```bash
+cd typescript
+make setup
+```
+
+> NOTE: If it fails for some reason, you'll need to install [uv](https://github.com/astral-sh/uv) manually.
+>
+> You can install it with:
+>
+> ```bash
+> curl -LsSf https://astral.sh/uv/install.sh | sh
+> ```
+>
+> Now you can try running `make setup` again, or simply `uv sync`.
+
+You now have the dependencies installed.
+
+Run `make help` to see all the available actions!
+
+## Tasks
+
+The entry-point to run commands and tasks is the `make` Python script, located in the `scripts` directory. Try running `make` to show the available commands and tasks. The *commands* do not need the Python dependencies to be installed,
+while the *tasks* do. The cross-platform tasks are written in Python, thanks to [duty](https://github.com/pawamoy/duty).
+
+If you work in VSCode, we provide [an action to configure VSCode](https://pawamoy.github.io/copier-uv/work/#vscode-setup) for the project.
+
+## Development
+
+As usual:
+
+1. create a new branch: `git switch -c feature-or-bugfix-name`
+1. edit the code and/or the documentation
+
+**Before committing:**
+
+1. run `make format` to auto-format the code
+1. run `make check` to check everything (fix any warning)
+1. run `make test` to run the tests (fix any issue)
+1. if you updated the documentation or the project dependencies:
+    1. run `make docs`
+    1. go to http://localhost:8000 and check that everything looks good
+1. follow our [commit message convention](#commit-message-convention)
+
+If you are unsure about how to fix or ignore a warning, just let the continuous integration fail, and we will help you during review.
+
+Don't bother updating the changelog, we will take care of this.
+
+## Commit message convention
+
+Commit messages must follow our convention based on the [Angular style](https://gist.github.com/stephenparish/9941e89d80e2bc58a153#format-of-the-commit-message) or the [Karma convention](https://karma-runner.github.io/4.0/dev/git-commit-msg.html):
+
+```
+<type>[(scope)]: Subject
+
+[Body]
+```
+
+**Subject and body must be valid Markdown.** Subject must have proper casing (uppercase for first letter if it makes sense), but no dot at the end, and no punctuation in general.
+
+Scope and body are optional. Type can be:
+
+- `build`: About packaging, building wheels, etc.
+- `chore`: About packaging or repo/files management.
+- `ci`: About Continuous Integration.
+- `deps`: Dependencies update.
+- `docs`: About documentation.
+- `feat`: New feature.
+- `fix`: Bug fix.
+- `perf`: About performance.
+- `refactor`: Changes that are not features or bug fixes.
+- `style`: A change in code style/format.
+- `tests`: About tests.
+
+If you write a body, please add trailers at the end (for example issues and PR references, or co-authors), without relying on GitHub's flavored Markdown:
+
+```
+Body.
+
+Issue #10: https://github.com/namespace/project/issues/10
+Related to PR namespace/other-project#15: https://github.com/namespace/other-project/pull/15
+```
+
+These "trailers" must appear at the end of the body, without any blank lines between them. The trailer title can contain any character except colons `:`. We expect a full URI for each trailer, not just GitHub autolinks (for example, full GitHub URLs for commits and issues, not the hash or the #issue-number).
+
+We do not enforce a line length on commit messages summary and body, but please avoid very long summaries, and very long lines in the body, unless they are part of code blocks that must not be wrapped.
+
+## Pull requests guidelines
+
+Link to any related issue in the Pull Request message.
+
+During the review, we recommend using fixups:
+
+```bash
+# SHA is the SHA of the commit you want to fix
+git commit --fixup=SHA
+```
+
+Once all the changes are approved, you can squash your commits:
+
+```bash
+git rebase -i --autosquash main
+```
+
+And force-push:
+
+```bash
+git push -f
+```
+
+If this seems all too complicated, you can push or force-push each new commit, and we will squash them ourselves if needed, before merging.

mkdocstrings_typescript-0.1.0/LICENSE

@@ -0,0 +1,15 @@
+ISC License
+
+Copyright (c) 2023, Timothée Mazzucotelli
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

mkdocstrings_typescript-0.1.0/PKG-INFO

@@ -0,0 +1,124 @@
+Metadata-Version: 2.4
+Name: mkdocstrings-typescript
+Version: 0.1.0
+Summary: A Typescript handler for mkdocstrings.
+Author-Email: =?utf-8?q?Timoth=C3=A9e_Mazzucotelli?= <dev@pawamoy.fr>
+License-Expression: ISC
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Documentation
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Classifier: Typing :: Typed
+Project-URL: Homepage, https://mkdocstrings.github.io/typescript
+Project-URL: Documentation, https://mkdocstrings.github.io/typescript
+Project-URL: Changelog, https://mkdocstrings.github.io/typescript/changelog
+Project-URL: Repository, https://github.com/mkdocstrings/typescript
+Project-URL: Issues, https://github.com/mkdocstrings/typescript/issues
+Project-URL: Discussions, https://github.com/mkdocstrings/typescript/discussions
+Project-URL: Gitter, https://gitter.im/mkdocstrings/typescript
+Project-URL: Funding, https://github.com/sponsors/pawamoy
+Requires-Python: >=3.10
+Requires-Dist: mkdocstrings>=0.28.3
+Requires-Dist: griffe-typedoc>=0.1
+Description-Content-Type: text/markdown
+
+# mkdocstrings-typescript
+
+[![ci](https://github.com/mkdocstrings/typescript/workflows/ci/badge.svg)](https://github.com/mkdocstrings/typescript/actions?query=workflow%3Aci)
+[![documentation](https://img.shields.io/badge/docs-mkdocs-708FCC.svg?style=flat)](https://mkdocstrings.github.io/typescript/)
+[![pypi version](https://img.shields.io/pypi/v/mkdocstrings-typescript.svg)](https://pypi.org/project/mkdocstrings-typescript/)
+[![gitter](https://badges.gitter.im/join%20chat.svg)](https://app.gitter.im/#/room/#typescript:gitter.im)
+
+A Typescript handler for mkdocstrings.
+
+WARNING: **Still in prototyping phase!**
+Feedback is welcome.
+
+## Installation
+
+```bash
+pip install mkdocstrings-typescript
+```
+
+## Usage
+
+Add these [TypeDoc](https://typedoc.org/) configuration files to your repository:
+
+```tree hl_lines="4 5"
+./
+    src/
+        package1/
+    typedoc.base.json
+    typedoc.json
+```
+
+```json title="typedoc.base.json"
+{
+  "$schema": "https://typedoc.org/schema.json",
+  "includeVersion": true
+}
+```
+
+```json title="typedoc.json"
+{
+  "extends": ["./typedoc.base.json"],
+  "entryPointStrategy": "packages",
+  "entryPoints": ["./src/*"]
+}
+```
+
+Update the entrypoints to match your file layout so that TypeDoc can find your packages. See [TypeDoc's configuration documentation](https://typedoc.org/options/configuration/).
+
+Then in each of your package, add this TypeDoc configuration file:
+
+```tree hl_lines="4"
+./
+    src/
+        package1/
+            typedoc.json
+    typedoc.base.json
+    typedoc.json
+```
+
+```json title="typedoc.json"
+{
+  "extends": ["../../typedoc.base.json"],
+  "entryPointStrategy": "expand",
+  "entryPoints": ["src/index.d.ts"]
+}
+```
+
+Again, update entrypoints to match your file and package layout. See [TypeDoc's configuration documentation](https://typedoc.org/options/configuration/).
+
+**Your packages must be built for TypeDoc to work.**
+
+You are now able to use the TypeScript handler to inject API docs in your Markdown pages by referencing package names:
+
+```md
+::: @owner/packageName
+    handler: typescript
+```
+
+You can set the Typescript handler as default handler:
+
+```yaml
+plugins:
+- mkdocstrings:
+    default_handler: typescript
+```
+
+By setting it as default handler you can omit it when injecting documentation:
+
+```md
+::: @owner/packageName
+```

mkdocstrings_typescript-0.1.0/README.md

@@ -0,0 +1,90 @@
+# mkdocstrings-typescript
+
+[![ci](https://github.com/mkdocstrings/typescript/workflows/ci/badge.svg)](https://github.com/mkdocstrings/typescript/actions?query=workflow%3Aci)
+[![documentation](https://img.shields.io/badge/docs-mkdocs-708FCC.svg?style=flat)](https://mkdocstrings.github.io/typescript/)
+[![pypi version](https://img.shields.io/pypi/v/mkdocstrings-typescript.svg)](https://pypi.org/project/mkdocstrings-typescript/)
+[![gitter](https://badges.gitter.im/join%20chat.svg)](https://app.gitter.im/#/room/#typescript:gitter.im)
+
+A Typescript handler for mkdocstrings.
+
+WARNING: **Still in prototyping phase!**
+Feedback is welcome.
+
+## Installation
+
+```bash
+pip install mkdocstrings-typescript
+```
+
+## Usage
+
+Add these [TypeDoc](https://typedoc.org/) configuration files to your repository:
+
+```tree hl_lines="4 5"
+./
+    src/
+        package1/
+    typedoc.base.json
+    typedoc.json
+```
+
+```json title="typedoc.base.json"
+{
+  "$schema": "https://typedoc.org/schema.json",
+  "includeVersion": true
+}
+```
+
+```json title="typedoc.json"
+{
+  "extends": ["./typedoc.base.json"],
+  "entryPointStrategy": "packages",
+  "entryPoints": ["./src/*"]
+}
+```
+
+Update the entrypoints to match your file layout so that TypeDoc can find your packages. See [TypeDoc's configuration documentation](https://typedoc.org/options/configuration/).
+
+Then in each of your package, add this TypeDoc configuration file:
+
+```tree hl_lines="4"
+./
+    src/
+        package1/
+            typedoc.json
+    typedoc.base.json
+    typedoc.json
+```
+
+```json title="typedoc.json"
+{
+  "extends": ["../../typedoc.base.json"],
+  "entryPointStrategy": "expand",
+  "entryPoints": ["src/index.d.ts"]
+}
+```
+
+Again, update entrypoints to match your file and package layout. See [TypeDoc's configuration documentation](https://typedoc.org/options/configuration/).
+
+**Your packages must be built for TypeDoc to work.**
+
+You are now able to use the TypeScript handler to inject API docs in your Markdown pages by referencing package names:
+
+```md
+::: @owner/packageName
+    handler: typescript
+```
+
+You can set the Typescript handler as default handler:
+
+```yaml
+plugins:
+- mkdocstrings:
+    default_handler: typescript
+```
+
+By setting it as default handler you can omit it when injecting documentation:
+
+```md
+::: @owner/packageName
+```

mkdocstrings_typescript-0.1.0/config/coverage.ini

@@ -0,0 +1,25 @@
+[coverage:run]
+branch = true
+parallel = true
+source =
+  src/
+  tests/
+
+[coverage:paths]
+equivalent =
+  src/
+  .venv/lib/*/site-packages/
+  .venvs/*/lib/*/site-packages/
+
+[coverage:report]
+precision = 2
+omit =
+  src/*/__init__.py
+  src/*/__main__.py
+  tests/__init__.py
+exclude_lines =
+  pragma: no cover
+  if TYPE_CHECKING
+
+[coverage:json]
+output = htmlcov/coverage.json

mkdocstrings_typescript-0.1.0/config/git-changelog.toml

@@ -0,0 +1,9 @@
+bump = "auto"
+convention = "angular"
+in-place = true
+output = "CHANGELOG.md"
+parse-refs = false
+parse-trailers = true
+sections = ["build", "deps", "feat", "fix", "refactor"]
+template = "keepachangelog"
+versioning = "pep440"

mkdocstrings_typescript-0.1.0/config/mypy.ini

@@ -0,0 +1,7 @@
+[mypy]
+ignore_missing_imports = true
+exclude = tests/fixtures/
+warn_unused_ignores = true
+show_error_codes = true
+namespace_packages = true
+explicit_package_bases = true

mkdocstrings_typescript-0.1.0/config/pytest.ini

@@ -0,0 +1,14 @@
+[pytest]
+python_files =
+  test_*.py
+addopts =
+  --cov
+  --cov-config config/coverage.ini
+testpaths =
+  tests
+
+# action:message_regex:warning_class:module_regex:line
+filterwarnings =
+  error
+  # TODO: remove once pytest-xdist 4 is released
+  ignore:.*rsyncdir:DeprecationWarning:xdist

mkdocstrings_typescript-0.1.0/config/ruff.toml

@@ -0,0 +1,91 @@
+target-version = "py39"
+line-length = 120
+
+[lint]
+exclude = [
+    "tests/fixtures/*.py",
+]
+select = [
+    "A", "ANN", "ARG",
+    "B", "BLE",
+    "C", "C4",
+    "COM",
+    "D", "DTZ",
+    "E", "ERA", "EXE",
+    "F", "FBT",
+    "G",
+    "I", "ICN", "INP", "ISC",
+    "N",
+    "PGH", "PIE", "PL", "PLC", "PLE", "PLR", "PLW", "PT", "PYI",
+    "Q",
+    "RUF", "RSE", "RET",
+    "S", "SIM", "SLF",
+    "T", "T10", "T20", "TCH", "TID", "TRY",
+    "UP",
+    "W",
+    "YTT",
+]
+ignore = [
+    "A001",  # Variable is shadowing a Python builtin
+    "ANN101",  # Missing type annotation for self
+    "ANN102",  # Missing type annotation for cls
+    "ANN204",  # Missing return type annotation for special method __str__
+    "ANN401",  # Dynamically typed expressions (typing.Any) are disallowed
+    "ARG005",  # Unused lambda argument
+    "C901",  # Too complex
+    "D105",  # Missing docstring in magic method
+    "D417",  # Missing argument description in the docstring
+    "E501",  # Line too long
+    "ERA001",  # Commented out code
+    "G004",  # Logging statement uses f-string
+    "PLR0911",  # Too many return statements
+    "PLR0912",  # Too many branches
+    "PLR0913",  # Too many arguments to function call
+    "PLR0915",  # Too many statements
+    "SLF001", # Private member accessed
+    "TRY003",  # Avoid specifying long messages outside the exception class
+]
+
+[lint.per-file-ignores]
+"src/**/cli.py" = [
+    "T201",  # Print statement
+]
+"src/*/debug.py" = [
+    "T201",  # Print statement
+]
+"!src/*/*.py" = [
+    "D100",  # Missing docstring in public module
+]
+"!src/**.py" = [
+    "D101",  # Missing docstring in public class
+    "D103",  # Missing docstring in public function
+]
+"scripts/*.py" = [
+    "INP001",  # File is part of an implicit namespace package
+    "T201",  # Print statement
+]
+"tests/**.py" = [
+    "ARG005",  # Unused lambda argument
+    "FBT001",  # Boolean positional arg in function definition
+    "PLR2004",  # Magic value used in comparison
+    "S101",  # Use of assert detected
+]
+
+[lint.flake8-quotes]
+docstring-quotes = "double"
+
+[lint.flake8-tidy-imports]
+ban-relative-imports = "all"
+
+[lint.isort]
+known-first-party = ["mkdocstrings_handlers.typescript"]
+
+[lint.pydocstyle]
+convention = "google"
+
+[format]
+exclude = [
+    "tests/fixtures/*.py",
+]
+docstring-code-format = true
+docstring-code-line-length = 80