Adding options for domParserOptions

[rntgspr]

Adding options for domParserOptions using Object.assign before send it directly to the parser itself;
Setting up a default value for domParserOptions;

Consider a possible refactoring, I am using github interface to update it.

I believe it closes #62

update:
I give up from this PR because we need a different solution to write raw strings on a React components. I believed to be logic to this repo do it, but actually it did not makes sense, crossing HTML/JSX/React Documentations.

[coveralls]

Coverage decreased (-0.7%) to 98.485% when pulling fc8b224 on rntgspr:master into bfe2023 on remarkablemark:master.

[remarkablemark]

Thanks for creating the PR @rntgspr. I added a comment and could you also handle the tasks:

• Run npm run lint:fix to make the CI build pass
• Add tests

[remarkablemark]

@rntgspr What is the warning that you get?

[remarkablemark]

@rntgspr Did you close this PR intentionally? If so, let me know what I can do to help you get this merged in because I believe the feature here is useful

[rntgspr]

Yes,

It can be useful, but it no matches with all documentations together.

1- warnings from ReactJS (warnings, self explanatory);
2- self-close from JSX(it always open and closes custom self-closed tags, it don't works in all possible scenarios);
3- lowercase from HTML5(take a look on: Use Lower Case Element Names section);

best,
Gaspar

[remarkablemark]

Thanks for the update @rntgspr. I appreciate the effort and I'll borrow some things from this PR to make as feature enhancements.