-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Namsonx/task/stabi branch #296
Conversation
Test cases JPP_1500 and JPP_1501 retested and reworked
(additional brackets and spaces)
* JPP_1003 updated * Code snippet generator updated
…_maintenance Self test maintenance:
…_maintenance Code snippet generator extended ('+' / '-' combinations in indices)
…_maintenance Documentation updated (JSONP format)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Son,
History: "Improved error message logs"
We do not have error message logs. Maybe you mean: Improved error messages?
No need to mention "logs", because some error messages are also written to console.
Therefore "Improved error messages" is enough.
You increased the version number from 0.5.0 to 0.5.1. This indicates a patch. But when you implement a new feature like the blocking of dynamic key names and the changed data type of the return value, this is not a patch any more. Please change the version to 0.6.0.
Hi Son, release info: Please keep the example simple. There is no need to use a nested dictionary to explain the blocked dynamic key names. This code also does - and is much easier to capture:
You can tell that "XYZ" now will not be created any more. And you should add a hint telling what happens instead of this: the error message. |
Hi Son, regarding:
caused by
Please separate this. Here we speak about two different things and it's unfavorable to mixup them. Also the wording needs to be fixed. Better: (1)
(2) And exchange:
by:
|
Hi Son, In case of a missing quotation, e.g:
I get an empty ERROR line:
Please remove the empty line or fill with content. |
Hi Son, please also consider |
Hello Thomas, From my site, this pull-request is ready to merge. Thank you, |
No description provided.