Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93008
  +product: App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductType {#93201
  +product: App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#93276
  +product: App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93699
    #id: 10560
    #code: "IEEE00004607"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039137 {#93706
      date: 2025-06-27 17:45:37.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#93685
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 37249
        #name: "IEEE 1044:2009"
        #slug: "ieee-1044-2009-ieee00004607-242212"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard provides a uniform approach to the classification of software anomalies, regardless of when they originate or when they are encountered within the project, product, or system lifecycle. Classification data can be used for a variety of purposes, including defect causal analysis, project management, and software process improvement (e.g., to reduce the likelihood of defect insertion and/or increase the likelihood of early defect detection).<br />\n
          \t\t\t\t<br />\n
          This standard provides for the core set of attributes for classification of failures and defects. It is recognized that there are other attributes of failures or defects that are of unique value to specific applications or business requirements. This standard is applicable to any software (including operating systems, database management systems, applications, testware, firmware, and embedded software) and to any phase of the project, product, or system life cycle by which the software is developed, operated, and sustained.<br />\n
          Classification attributes are unaffected by the choice of life cycle model, and that choice is outside the scope of this standard. Some tailoring of classification attribute values based on the chosen life cycle is expected and consistent with the intent of this standard.<br />\n
          The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93669
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1586210400 {#93705
      date: 2020-04-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1262818800 {#93704
      date: 2010-01-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#93698
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106852
  +product: App\Entity\Product\Product {#93699
    #id: 10560
    #code: "IEEE00004607"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039137 {#93706
      date: 2025-06-27 17:45:37.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#93685
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 37249
        #name: "IEEE 1044:2009"
        #slug: "ieee-1044-2009-ieee00004607-242212"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard provides a uniform approach to the classification of software anomalies, regardless of when they originate or when they are encountered within the project, product, or system lifecycle. Classification data can be used for a variety of purposes, including defect causal analysis, project management, and software process improvement (e.g., to reduce the likelihood of defect insertion and/or increase the likelihood of early defect detection).<br />\n
          \t\t\t\t<br />\n
          This standard provides for the core set of attributes for classification of failures and defects. It is recognized that there are other attributes of failures or defects that are of unique value to specific applications or business requirements. This standard is applicable to any software (including operating systems, database management systems, applications, testware, firmware, and embedded software) and to any phase of the project, product, or system life cycle by which the software is developed, operated, and sustained.<br />\n
          Classification attributes are unaffected by the choice of life cycle model, and that choice is outside the scope of this standard. Some tailoring of classification attribute values based on the chosen life cycle is expected and consistent with the intent of this standard.<br />\n
          The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93669
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1586210400 {#93705
      date: 2020-04-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1262818800 {#93704
      date: 2010-01-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#93698
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93699
    #id: 10560
    #code: "IEEE00004607"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039137 {#93706
      date: 2025-06-27 17:45:37.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#93685
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 37249
        #name: "IEEE 1044:2009"
        #slug: "ieee-1044-2009-ieee00004607-242212"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard provides a uniform approach to the classification of software anomalies, regardless of when they originate or when they are encountered within the project, product, or system lifecycle. Classification data can be used for a variety of purposes, including defect causal analysis, project management, and software process improvement (e.g., to reduce the likelihood of defect insertion and/or increase the likelihood of early defect detection).<br />\n
          \t\t\t\t<br />\n
          This standard provides for the core set of attributes for classification of failures and defects. It is recognized that there are other attributes of failures or defects that are of unique value to specific applications or business requirements. This standard is applicable to any software (including operating systems, database management systems, applications, testware, firmware, and embedded software) and to any phase of the project, product, or system life cycle by which the software is developed, operated, and sustained.<br />\n
          Classification attributes are unaffected by the choice of life cycle model, and that choice is outside the scope of this standard. Some tailoring of classification attribute values based on the chosen life cycle is expected and consistent with the intent of this standard.<br />\n
          The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93669
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1586210400 {#93705
      date: 2020-04-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1262818800 {#93704
      date: 2010-01-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#93698
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
]

App\Twig\Components\ProductMostRecent {#106924
  +product: App\Entity\Product\Product {#93699
    #id: 10560
    #code: "IEEE00004607"
    #attributes: Doctrine\ORM\PersistentCollection {#93679 …}
    #variants: Doctrine\ORM\PersistentCollection {#93676 …}
    #options: Doctrine\ORM\PersistentCollection {#93672 …}
    #associations: Doctrine\ORM\PersistentCollection {#93668 …}
    #createdAt: DateTime @1751039137 {#93706
      date: 2025-06-27 17:45:37.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#93685
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93690 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93731
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93699}
        #id: 37249
        #name: "IEEE 1044:2009"
        #slug: "ieee-1044-2009-ieee00004607-242212"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard provides a uniform approach to the classification of software anomalies, regardless of when they originate or when they are encountered within the project, product, or system lifecycle. Classification data can be used for a variety of purposes, including defect causal analysis, project management, and software process improvement (e.g., to reduce the likelihood of defect insertion and/or increase the likelihood of early defect detection).<br />\n
          \t\t\t\t<br />\n
          This standard provides for the core set of attributes for classification of failures and defects. It is recognized that there are other attributes of failures or defects that are of unique value to specific applications or business requirements. This standard is applicable to any software (including operating systems, database management systems, applications, testware, firmware, and embedded software) and to any phase of the project, product, or system life cycle by which the software is developed, operated, and sustained.<br />\n
          Classification attributes are unaffected by the choice of life cycle model, and that choice is outside the scope of this standard. Some tailoring of classification attribute values based on the chosen life cycle is expected and consistent with the intent of this standard.<br />\n
          The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.The purpose of this standard is to define a common vocabulary with which different people and organizations can communicate effectively about software anomalies and to establish a common set of attributes that support industry techniques for analyzing software defect and failure data.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93688 …}
    #channels: Doctrine\ORM\PersistentCollection {#93681 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93686 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93683 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93696 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93669
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1586210400 {#93705
      date: 2020-04-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1262818800 {#93704
      date: 2010-01-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1583362800 {#93698
      date: 2020-03-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 23
    -documents: Doctrine\ORM\PersistentCollection {#93694 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93692 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106989
  +product: App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#107016
  +product: App\Entity\Product\Product {#7311
    #id: 9051
    #code: "IEEE00001526"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751037930 {#7274
      date: 2025-06-27 17:25:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 31213
        #name: "IEEE 1044:1993 (R2002)"
        #slug: "ieee-1044-1993-r2002-ieee00001526-240703"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A uniform approach to the classification of anomalies found in software and its documentation is provided. The processing of anomalies discovered during any software life cycle phase are described, and comprehensive lists of software anomaly classifications and related data items that are helpful to identify and track anomalies are provided. This standard is not intended to define procedural or format requirements for using the classification scheme. It does identify some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          \t\t\t\t<br />\n
          This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations. To accomplish the classification task, this standard documents the following subjects:<br />\n
          (a) Definitions of terms not provided in IEEE Std 610.12-1990 (b)A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information (c) A standard set of categories and classifications, either mandatory or optional (d) A list of supporting data items.<br />\n
          This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.<br />\n
          The classifications are layered with greater detail in each subsequent layer. For instance, in the Project phase category has two levels of classifications, and in the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.<br />\n
          The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Classification for Software Anomalies"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @754614000 {#7318
      date: 1993-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#7316
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1044"
    -bookCollection: ""
    -pageCount: 32
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#128473
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128456 …}
    #variants: Doctrine\ORM\PersistentCollection {#128454 …}
    #options: Doctrine\ORM\PersistentCollection {#128449 …}
    #associations: Doctrine\ORM\PersistentCollection {#128451 …}
    #createdAt: DateTime @1751037622 {#128446
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128481
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128467 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128558
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128473}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128465 …}
    #channels: Doctrine\ORM\PersistentCollection {#128458 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128462 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128460 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128475 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128432
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128480
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128439
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128452
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128471 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128469 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#128529
  +product: App\Entity\Product\Product {#128473
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128456 …}
    #variants: Doctrine\ORM\PersistentCollection {#128454 …}
    #options: Doctrine\ORM\PersistentCollection {#128449 …}
    #associations: Doctrine\ORM\PersistentCollection {#128451 …}
    #createdAt: DateTime @1751037622 {#128446
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128481
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128467 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128558
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128473}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128465 …}
    #channels: Doctrine\ORM\PersistentCollection {#128458 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128462 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128460 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128475 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128432
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128480
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128439
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128452
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128471 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128469 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}

[
  "product" => App\Entity\Product\Product {#128473
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128456 …}
    #variants: Doctrine\ORM\PersistentCollection {#128454 …}
    #options: Doctrine\ORM\PersistentCollection {#128449 …}
    #associations: Doctrine\ORM\PersistentCollection {#128451 …}
    #createdAt: DateTime @1751037622 {#128446
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128481
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128467 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128558
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128473}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128465 …}
    #channels: Doctrine\ORM\PersistentCollection {#128458 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128462 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128460 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128475 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128432
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128480
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128439
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128452
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128471 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128469 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#128562
  +product: App\Entity\Product\Product {#128473
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128456 …}
    #variants: Doctrine\ORM\PersistentCollection {#128454 …}
    #options: Doctrine\ORM\PersistentCollection {#128449 …}
    #associations: Doctrine\ORM\PersistentCollection {#128451 …}
    #createdAt: DateTime @1751037622 {#128446
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128481
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128467 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128558
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128473}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128465 …}
    #channels: Doctrine\ORM\PersistentCollection {#128458 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128462 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128460 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128475 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128432
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128480
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128439
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128452
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128471 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128469 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#128473
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128456 …}
    #variants: Doctrine\ORM\PersistentCollection {#128454 …}
    #options: Doctrine\ORM\PersistentCollection {#128449 …}
    #associations: Doctrine\ORM\PersistentCollection {#128451 …}
    #createdAt: DateTime @1751037622 {#128446
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128481
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128467 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128558
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128473}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128465 …}
    #channels: Doctrine\ORM\PersistentCollection {#128458 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128462 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128460 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128475 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128432
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128480
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128439
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128452
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128471 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128469 …}
  }
]

App\Twig\Components\ProductMostRecent {#128640
  +product: App\Entity\Product\Product {#128473
    #id: 8683
    #code: "IEEE00000855"
    #attributes: Doctrine\ORM\PersistentCollection {#128456 …}
    #variants: Doctrine\ORM\PersistentCollection {#128454 …}
    #options: Doctrine\ORM\PersistentCollection {#128449 …}
    #associations: Doctrine\ORM\PersistentCollection {#128451 …}
    #createdAt: DateTime @1751037622 {#128446
      date: 2025-06-27 17:20:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#128481
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128467 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128558
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128473}
        #id: 29741
        #name: "IEEE 610.12:1990 (R2002)"
        #slug: "ieee-610-12-1990-r2002-ieee00000855-240335"
        #description: """
          Revision Standard - Superseded.<br />\n
          This standard identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.<br />\n
          \t\t\t\t<br />\n
          This glossary defines terms in the field of Software Engineering. Topics covered include addressing; assembling, compiling, linking, loading; computer performance evaluation; configuration management; data types; errors, faults, and failures; evaluation techniques; instruction types; language types;<br />\n
          libraries; microprogramming; operating systems; quality attributes; software documentation; software and system testing; software architecture; software development process; software development techniques; and software tools.<br />\n
          Every effort has been made to include all terms that meet these criteria. Terms were excluded if they were considered to be parochial to one group or organization; company proprietary or trademarked; multi-word terms whose meaning could be inferred from the definitions of the component words; or terms whose meaning in the computer field could be directly inferred from their standard English meaning.<br />\n
          This glossary is an update and expansion of IEEE Std 729-1983, IEEE Standard Glossary of Software Engineering Terminology (ANSI) L3I.l It increases the number of terms from approximately 500 to 1300, and updates or refines the definitions of many terms included in the initial glossary. A few terms that were included in the initial glossary have been moved to other glossaries in the 610 series. Some definitions have been recast in a system, rather than software, context. Every effort has been made to preserve the fine work that went into the initial glossary.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Glossary of Software Engineering Terminology"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#128465 …}
    #channels: Doctrine\ORM\PersistentCollection {#128458 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128462 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128460 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128475 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128432
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128480
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @662598000 {#128439
      date: 1990-12-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1031781600 {#128452
      date: 2002-09-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "610.12"
    -bookCollection: ""
    -pageCount: 84
    -documents: Doctrine\ORM\PersistentCollection {#128471 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128469 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}