Skip to content

Form documentation enhancements #1220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

RedZone908
Copy link
Contributor

Types of Changes

Prerequisites

Please make sure you can check the following two boxes:

  • I have read the CONTRIBUTING document
  • My code follows the code style of this project - Documentation change only, does this apply?

Contribution Type

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue, please reference the issue id)
  • New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed

Description

Added further documentation about different ways to use forms that were not obvious to me and not already described in existing documentation. I had to figure out one of these via StackOverflow, and the other one through my own trial and error. My main goal here was to help future users not run into the same pitfalls that I did.

This is something that I didn't even know could be done till I found an answer on StackOverflow detailing it, so I thought it might be helpful to put it right in the documentation.
This was a pitfall I encountered that I had to figure out myself. Hoping that documenting it can keep someone else from running into the same issue.
@CLAassistant
Copy link

CLAassistant commented Mar 24, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@FlorianRappl FlorianRappl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thanks!

@FlorianRappl FlorianRappl added this to the 1.3.0 milestone Mar 24, 2025
@FlorianRappl FlorianRappl merged commit 4f3f1aa into AngleSharp:devel Mar 24, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants