Parser class implementation #6

Closed
opened 2025-10-14 12:16:52 -07:00 by azpect · 1 comment
Owner

A parser class should exist, which will work in parallel with a DOM class that generates the HTML tree.

This will be a simple shell of the parser. A result will be a simple class with some method prototypes and use case examples.

This is not intended to define everything, but rather what the team is currently aware of.

A `parser` class should exist, which will work in parallel with a `DOM` class that generates the HTML tree. This will be a simple shell of the parser. A result will be a simple class with some method prototypes and use case examples. This is not intended to define **everything**, but rather what the team is currently aware of.
azpect added the
Kind/Feature
Priority
Critical
labels 2025-10-14 12:16:52 -07:00
azpect self-assigned this 2025-10-14 12:16:52 -07:00
azpect added this to the (SPRINT) Parser creation project 2025-10-14 12:16:52 -07:00
azpect moved this to To Do in (SPRINT) Parser creation on 2025-10-14 12:17:00 -07:00
azpect moved this to In Progress in (SPRINT) Parser creation on 2025-10-14 12:17:03 -07:00
Author
Owner

The parser is implemented, new features or parser rules will exist via new issues.

The parser is implemented, new features or parser rules will exist via new issues.
azpect moved this to Done in (SPRINT) Parser creation on 2025-10-17 13:19:57 -07:00
Sign in to join this conversation.
No description provided.