Custom typing generator #3152
Merged
Custom typing generator #3152
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
T4rk1n requested review from alexcjohnson, emilykl, gvwilson and ndrezn as code owners 
gvwilson approved these changes Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Add custom typing for component props, previously hardcoded for dcc.Graph.
Component libraries developer can add a file
dash_prop_typingcontaining one or two variables:custom_imports: dict[ComponentName, list[str]]import statement to be copied at the top of the component class definition.custom_props: dict[ComponentName, dict[PropName, function]]for custom props. The function signature is:def generate_type(type_info, component_name, prop_name) -> str.The module path can be changed with the
dash-generate-componentsargument-tor--custom-typing-module.