Custom parameters prefix knotx snippet

[malaskowski]

Description

Snippet parameters names are too long, because of being HTML5 compliant (as the snippet tag is <script>). Since Knot.x 1.2.1, it is possible to customize snippet tag name (see #385 for more details).
This enchancment is followup of this discusion.

Motivation and Context

• snippet parameters should enable defining HTML compliant prefixes, but when not necessary should be simplified.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

---

I hereby agree to the terms of the Knot.x Contributor License Agreement.

[pun-ky]

Type parameter was required for script tag. Is it still required when non script tag is used? / knotx:snippet?

[malaskowski]

@pun-ky thanks for this catch, of course it is not required.
I've updated wiki with information about it.
Good catch.

[marcinczeczko]

what about default values ? a good practice is to have private init() method invoked in default constructor and inside jsonobject constructor (before converter). an init method will simply set default values for tag and prefix. that way we avoid potential nullpointers

[malaskowski]

You're right. I first thought that there will be no default values, but this is very good place to have those.