-
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
Prevent hash / scalar manipulation #209
Comments
This as intentionally "allowed" to ease the conversion of the model |
Indeed; scalar values are automatically upgraded to a filter group collection where the value is under the empty key. This was done to allow piecemeal transition of existing code to have a breakdown of the values. So effectively the final result consists of the same total, with a breakdown of some of the value, and the rest of it considered uncategorized. I'm not especially attached to that, but given it has well-defined semantics and doesn't hurt the final total it seemed like a useful relaxation. Unlike when it was initially implemented, these days there is a way to tighten this up and still have the freedom in development: one can call |
The Problem with that is, that printing the output of the hash is rather confusing, since the entry for the 'uncategorized' key is not showing up:
|
Only done for the text output. In response to #209.
@zaucker Extend GUI Formatter. |
Add error vor hash operators (P+ etc) for use with scalars, e.g. following code added in File Application.nhd:
The text was updated successfully, but these errors were encountered: