We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
text
Expected behaviour: element.firstChild(tag: "text") return first text node instead of element node with tag name "text"
Actual behaviour: returns element not text node
Package Manager: CocoaPods, version: 1.11.2
Fuzi version: 3.1.3
Xcode version: 13.4
<parent> <text>Some text</text> </parent>
parent.firstChild(tag: "text")?.stringValue == " \n" instead of parent.firstChild(tag: "text")?.stringValue == "Some text" parent.firstChild(tag: "text")?.type == .Text instead of parent.firstChild(tag: "text")?.type == .Element
parent.firstChild(tag: "text")?.stringValue == " \n"
parent.firstChild(tag: "text")?.stringValue == "Some text"
parent.firstChild(tag: "text")?.type == .Text
parent.firstChild(tag: "text")?.type == .Element
parent.children(tag: "text") finds proper nodes as it checks also element type
parent.children(tag: "text")
The text was updated successfully, but these errors were encountered:
@cezheng please have a look at #121
Sorry, something went wrong.
No branches or pull requests
Description:
Expected behaviour:
element.firstChild(tag: "text") return first text node instead of element node with tag name "text"
Actual behaviour: returns element not text node
Environment
Package Manager:
CocoaPods, version: 1.11.2
Fuzi version: 3.1.3
Xcode version: 13.4
How to reproduce:
parent.firstChild(tag: "text")?.stringValue == " \n"
instead ofparent.firstChild(tag: "text")?.stringValue == "Some text"
parent.firstChild(tag: "text")?.type == .Text
instead ofparent.firstChild(tag: "text")?.type == .Element
parent.children(tag: "text")
finds proper nodes as it checks also element typeThe text was updated successfully, but these errors were encountered: