When using AnQiCMS for website content management, we often encounter scenarios where we need to make judgments and process data. Especially when the data comes from user input or external interfaces and its type is uncertain, how to handle it in the template'sifCondition judgment correctly identified through.floatorintegerThe number converted by the filter is the key to ensuring logical accuracy.

The template engine feature of AnQiCMS is powerful, supporting GoLang.floatandintegerUnderstanding these conversion filters and their behavior in different situations is crucial for writing robust and reliable template logic.

Understand the 'true' and 'false' in AnQiCMS templates

In the template logic of AnQiCMS, like many programming languages, certain non-boolean values are implicitly considered 'true' or 'false' when performing conditional judgments.This feature is usually referred to as 'truthiness'.

For numeric types, the judgment rules of the AnQiCMS template engine are very intuitive:

  • Integer (integer):0被视为“false”（false），而任何非零整数（包括正数和负数）都被视为“true”（true).
  • 浮点数（float）:0.0被视为“false”（false）while any non-zero floating-point number is considered “true”true).

This means that if you use a numeric variable directly in aifcondition,{% if myNumber %}The system will automatically judge its truth or falsity according to the above rules.

floatWithintegerThe key behavior of the filter

AnQiCMS providesfloatandintegerThese filters are used to convert variables to their corresponding numeric types. Their usage is very simple:

  • {{ value|float }}Attempt to convertvalueto a floating-point number.
  • {{ value|integer }}Attempt to convertvalueto an integer.

The 'magic' of these filters lies in how they handleConversion failedthe behavior when passedfloatorintegerWhen the value of the filter cannot be effectively converted to a number, it will not throw an error, but will return adefault zero value:

  • value|floatwhen the conversion fails0.0.
  • value|integerwhen the conversion fails0.

This default behavior of returning zero is ingeniously combined with the true value judgment rules of AnQiCMS template engine, providing us with a reliable conditional judgment mechanism.

Practical Practice: Ensuring the Accuracy of Conditional Judgment

Assuming we have a variable obtained from an external sourceuser_scoreIt may be a numeric string (such as "100"), a floating-point number string (such as "99.5"), or an invalid string (such as "N/A").We want to decide whether to display some content based on this score.

  1. Handling Valid Numeric StringIfuser_scoreIt's '100', we convert it to an integer or floating-point number:

    {% set score_int = user_score|integer %}
{% if score_int %}
    <p>用户分数为有效非零值：{{ score_int }}</p>
{% endif %}

    At this time,score_intit will be100,"inifrecognized astrue, and the content will be displayed normally.

  2. Handling floating-point number conversionIfuser_scoreThe value is '99.5', we convert it to a floating-point number:

    {% set score_float = user_score|float %}
{% if score_float %}
    <p>用户分数为有效非零浮点值：{{ score_float }}</p>
{% endif %}

    At this time,score_floatit will be99.5,"inifrecognized astrue, and the content will be displayed normally.

  3. Handle invalid stringIfuser_scoreThe value is 'N/A' or 'unknown', we try to convert it:

    {% set score_int = user_score|integer %}
{% if score_int %}
    <p>用户分数为有效非零值：{{ score_int }}</p>
{% else %}
    <p>用户分数无效或为零。</p>
{% endif %}

    Whenuser_scoreWhen the value is 'N/A',score_intit will be0(Because the conversion failed). Inifthe condition,0is recognized asfalse, therefore it will executeelsea branch, displaying 'User score is invalid or zero.'

  4. Process meaningful zero valuesIfuser_scoreIt is "0" or "0.0", and it is a meaningful zero score; we still want it to be recognized as "false":

    {% set score_int = user_score|integer %}
{% if score_int %}
    <p>用户分数为有效非零值：{{ score_int }}</p>
{% else %}
    <p>用户分数是零或无效。</p>
{% endif %}

    At this time,score_intit will be0,"inifrecognized asfalsewill also be executedelseBranch. This is in line with our intuitive judgment of zero.

As can be seen from the above examples,floatandintegerThe filter in AnQiCMS template not only completes data type conversion, but also cleverly returns zero values when the conversion fails.ifThe conditional judgment provides implicit boolean logic, making the judgment of 'invalid is false' exceptionally concise and efficient.

Summary

Ensure that the AnQiCMS template is accessed throughfloatorintegerThe converted number inifCondition judgment can be correctly identified astrueorfalseThe core lies in understanding the following two points:

  1. Zero value principle: Integer0and floating point number0.0InifCondition is consideredfalse; Any non-zero number is consideredtrue.
  2. Filter default:floatandintegerThe filter will return the default value if the conversion fails0.0or0.

Therefore, as long as the value to be judged is passed throughfloatorintegerThe filter performs a conversion, regardless of whether the original value is a valid numeric string or an invalid non-numeric string, the final result will be able to inifThis is correctly judged based on the zero principle in the condition. This greatly simplifies the conditional logic in the template, improving development efficiency.

Common Questions (FAQ)

  1. How to differentiate between a 'true zero' and a 'zero caused by conversion failure'?Under this default behavior,0and0.0(meaningful zero) and the zero after conversion failure0and0.0Inifwill be considered in the judgmentfalseIf you need to distinguish between these two cases, for example, to display "User has no score" instead of "Data is invalid", you may need to do something else first (such as regular expressions orcontainUse a filter (）to check if the original string matches the numeric format.If the original string is not a number, it can be explicitly considered as 'invalid data'; otherwise, it is a 'true zero'.

  2. Does this 'truthy' judgment rule also apply to strings and arrays?Yes, AnQiCMS template engine also has a similar 'truthy' judgment for other data types:

    • StringAn empty string is considered"")} is consideredfalse, any non-empty string (even if the content is "0" or "false") is consideredtrue.
    • an array/slice: An empty array/slice is consideredfalseAn array/slice containing any element is consideredtrue. These rules also help write concise conditional judgment logic.

  3. If I have a string"0", but inifI hope it is considered in the conditiontruebecause"0"it is a valid ID for me, how should I handle it?directly using{% if some_string %}It will"0"astruebecause it is a non-empty string. But if you convert it firstintegerconvert,{% if some_string|integer %}it will be treated asfalse. If you want to convert a string"0"astrue, the best way isAvoid implicit type conversionInsteadExplicit comparisonFor example,{% if some_string == "0" %}or{% if some_string == "0" or some_string|integer > 0 %}, which allows for more precise control of your judgment logic.