Doctrine Common
  1. Doctrine Common
  2. DCOM-38

Annotation parser plain value types


    • Type: Bug Bug
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.0.2
    • Component/s: Annotations
    • Labels:
    • Environment:



      I posted this question in doctrine user group(!topic/doctrine-user/QhAz-Yr70T0), but with no response, so I'd like to open it up here as the solution is trivial and would save me either a lot of sub-classing or prevent me from changing the doctrine library files.

      This annotation

      class SomeGrid {
           *  @GRID:Column(header="Reg. plate", width=80, editable=TRUE, hidden=FALSE, tooltip="Registration plate", align="left", sortable=TRUE)
          public $regPlate;

      produces the following object:

      (object) Grid\Annotations\Column {
          "header"   => (string) "Reg. plate"
          "width"    => (string) "80"
          "editable" => (bool)   true
          "hidden"   => (bool)   false
          "tooltip"  => (string) "Registration plate"
          "align"    => (string) "left"
          "sortable" => (bool)   true

      You can see the value of the width property is string even I didn't use quotes in the annotation.
      The same happens with float values, but true and false values become, correctly, bool.

      I found this happens because of the following fragment of code in \Doctrine\Common\Annotations\Parser and could be easily corrected by prefixing the value with the corresponding type cast (marked in red).

          case Lexer::T_STRING:
              return $this->lexer->token['value'];
          case Lexer::T_INTEGER:
              return (int)$this->lexer->token['value'];
          case Lexer::T_FLOAT:
              return (float)$this->lexer->token['value'];
          case Lexer::T_TRUE:
              return true;
          case Lexer::T_FALSE:
              return false;

      The point is, in our app, some of the values go directly to browser and are processed by JavaScript. Having those values as strings breaks all kinds of mathematical operations on the client or would require additional (unnecessary) string to int/float conversions.



          • Assignee:
            Benjamin Eberlei
            Martin Ivičič
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: