You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: xml5ever/README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ xml5ever is based largely on [html5ever](https://github.com/servo/html5ever) par
14
14
15
15
The library is dual licensed under MIT and Apache license.
16
16
17
-
#Why you should use xml5ever
17
+
#Why you should use xml5ever
18
18
19
19
Main use case for this library is when XML is badly formatted, usually from bad XML
20
20
templates. XML5 tries to handle most common errors, in a manner similar to HTML5.
@@ -32,7 +32,7 @@ templates. XML5 tries to handle most common errors, in a manner similar to HTML5
32
32
- You require an easy to use parser, with lots of extensions (e.g. XPath, XQuery).
33
33
- You require a battle tested, industry proven solution.
34
34
35
-
#Installation
35
+
#Installation
36
36
37
37
Add xml5ever as a dependency in your project manifest.
38
38
@@ -47,7 +47,7 @@ And add crate declaration in your lib.rs
47
47
externcrate xml5ever
48
48
```
49
49
50
-
#Getting started
50
+
#Getting started
51
51
52
52
Here is a very simple RcDom backed parser:
53
53
@@ -64,7 +64,7 @@ Here is a very simple RcDom backed parser:
64
64
```
65
65
The thing that does actual parsing is the `parse` function. It expects an iterator that can be converted into `StrTendril`, so you can use `std::iter::once(input)` or `Some(input).into_iter()` (where `input` is `StrTendril` like structure).
66
66
67
-
#Working on xml5ever
67
+
#Working on xml5ever
68
68
69
69
To build examples and tests you need to do something along the lines of:
70
70
@@ -78,7 +78,7 @@ This will fetch tests from outside repository and it will invoke cargo to
78
78
build and test the crate. If you need docs checkout either [API docs](https://ygg01.github.io/docs/xml5ever/xml5ever/index.html) or run `cargo docs`
79
79
to generate documentation.
80
80
81
-
##Easy first tasks
81
+
##Easy first tasks
82
82
83
83
What I generally recommend is to look at Clippy Linting badge results and create
84
84
a PR for fixing the said lints. Other than that try to look for any tasks labeled
0 commit comments