Christian Bewernitz

Results 40 issues of Christian Bewernitz

We are currently maintaining the type defeinitons in index.d.ts by hand and relying heavily on many interfaces/types provided by adding `/// `. Since the implementation differs in some significant ways,...

documentation
help-wanted
types

We just restored the existing `vows` test suite. But I don't think we should add new tests to it (or only in a limited manner). - there are many tests...

good first issue
help-wanted
question
strategic

As part of #321 a docstring was added to the implementation of `Node.lookupPrefix` including links to the expected implementation. - There seems to be some missing cases for some node...

documentation
help-wanted
needs investigation
spec:DOM Living Standard
spec:DOM Level 3

This is a continuation of https://github.com/jindw/xmldom/issues/267 which already contains an elaborate discussion. Two examples that are used in vue, are attributes starting with `:` or `@`. According to the XML...

bug
needs investigation
spec:XML
spec:Namespaces in XML
spec:HTML

@XhmikosR [suggested](https://github.com/xmldom/xmldom/pull/186#issuecomment-786466007) to make use of some of these eslint rules: https://github.com/mysticatea/eslint-plugin-node Which work based on the engines field in `package.json`. We are already using the `eslint-plugin-es5`, we should check...

needs investigation
code style

According [the specification this library is trying to implement](https://www.w3.org/TR/DOM-Level-2-Core/) it has been marked as "superseeded" in November 2020: > Status of this document > This section describes the status of...

documentation
question
strategic
spec:DOM-Level-2
spec:DOM Living Standard
spec:DOM Level 3

My initial issue was that I wanted to be able to write `npm-compare */` which in bash would pass the list of all subdirectories to the tool, but all end...

While trying to add a test for #40 I realized that the state machine I describe in #38 is not valid vor `xstate@3` but only for v4. Updating to version...

The main case I'm aware of is when an event only triggers actions but doesn't change the state. ``` { "initial": "initial", "states": { "initial": { "on": { "LOG": {...

The recommended setup suggests to not use webpack caching features, since it would be easier to add a commit hash at deployment time. Since the suggested method will produce new...