Enhancement 206 - Fix urgent issue of parameter name check

[namsonx]

Hello Thomas,

I created the small change for enhancement 206 - Validity pre-check for variable names for release 0.13.0.

Thank you,
Son

[HolQue]

Hi Son,

this change has side effects (compared with the JsonPreprocessor version from last month). And this change did not came from stabi branch, but from another one. Is the change in this branch made based on the stabi branch? Or in other words: Which branch shall I use for further testing while reworking the self test?

In earlier version I got this error message in case of a reserved keyword is used:

'The JSONP content contains a reserved token '__handleDuplicatedKey__00''

In this branch the error message is:

''int' object has no attribute 'pop'' (that is not like expected)

In current stabi branch the error message is correct:

'The JSONP content contains a reserved token '__handleDuplicatedKey__00''

And there are other differences. Maybe it's better to integrate this fix into the stabi branch and skip this branch.

[namsonx]

Hi Son,

this change has side effects (compared with the JsonPreprocessor version from last month). And this change did not came from stabi branch, but from another one. Is the change in this branch made based on the stabi branch? Or in other words: Which branch shall I use for further testing while reworking the self test?

In earlier version I got this error message in case of a reserved keyword is used:

'The JSONP content contains a reserved token '__handleDuplicatedKey__00''

In this branch the error message is:

''int' object has no attribute 'pop'' (that is not like expected)

In current stabi branch the error message is correct:

'The JSONP content contains a reserved token '__handleDuplicatedKey__00''

And there are other differences. Maybe it's better to integrate this fix into the stabi branch and skip this branch.

Hello Holger,

Actually, I created this commit (0edb72543) on stabi branch, then I created new branch namsonx/urgent/fix from develop branch and cherry-pick only this commit from stabi branch to namsonx/urgent/fix.

The purpose is: I found the issue with Enhancement 206, and the implementation of this enhancement already merged to develop branch.

I didn't merge stabi branch to develop branch due to there are many enhancements need the confirmation from you.

Regarding the issue The JSONP content contains a reserved token '__handleDuplicatedKey__00' you mentioned in your comment, it's fixed on stabi branch but not merged to develop branch yet. That the reason, you still observe this issue on namsonx/urgent/fix branch.

I hope my explanation is clear to you, and sorry for the inconvenience!

Thank you,
Son