Bug fixes and consistency fixes#8
Merged
Merged
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
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.
This pull request primarily updates the documentation and code examples to standardize the use of
Anchorfor hyperlinks instead ofLinkorHtmlLink, and clarifies the API for form fields. It also revises the ecosystem section in the documentation for clearer descriptions and adds new components. Below are the most important changes:Component and Example Refactoring:
LinkandHtmlLinkwithAnchorandLinkrespectively in code examples across multiple files (e.g.,examples/basic_usage.py,examples/context_managers.py,examples/custom_components.py,examples/framework_integration.py, andexamples/attributes_and_styles.py) to standardize hyperlink usage and clarify the distinction between anchor elements and link tags. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26]Documentation Improvements:
README.mdto a more general "AI Assistant Integration" section, clarifying how to add NitroUI knowledge to AI coding assistants.README.mdwith clearer, more descriptive summaries and added a new entry fornitro-image.Form Field API Clarification:
Field.*methods accept an optionalidparameter (defaulting toname) and forward additional keyword arguments to the underlying input, improving clarity for users of the API.checkedandvalueparameters.These changes improve consistency in code examples, enhance documentation clarity, and make the API easier to understand and use.