#1 fix nonstandard property parsing

[filecage]

Fixes #1 by no longer throwing for non-standard properties that are not prefixed with X- or IANA-

[passionate-bram]

There is a short-hand notation for constructors when the argument name matches the target field name.

https://www.typescriptlang.org/docs/handbook/2/classes.html#parameter-properties

This constructor would be written as:

constructor (public readonly value: T, public readonly parameters: P, public readonly isNonStandard: boolean = false) {}

// Same but multiline for readability
constructor(
  public readonly value: T,
  public readonly parameters: P,
  public readonly isNonStandard: boolean = false
) {}

Some linters complain about the empty constructor body which you can solve with an /* empty on purpose */ comment or similar.

Also note that in this case if there is additional logic besides the fields you can still have regular code in the constructor, the body executes after field assignments.

Edit1: Extended example
Edit2: Linked to correct section in the handbook, same page but different heading

[filecage]

@passionate-bram Nice, I didn't know about constructor parameter promotion in TypeScript yet. I'll update this soon. Thanks for your help!