GET https://dev.normadoc.fr/_partial/cart/add-item?productId=9374&template=%40SyliusShop%2FProduct%2FShow%2F_addToCart.html.twig

Response
200 OK
IP
216.73.216.37
Profiled on
Token
b3397d

Forms

  • sylius_add_to_cart
    • cartItem
    • _token

sylius_add_to_cart

Form type: 
"Sylius\Bundle\CoreBundle\Form\Type\Order\AddToCartType"

Errors

This form has no errors.

Default Data

Property Value
Model Format same as normalized format
Normalized Format 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106752
  -cart: App\Entity\Order\Order {#13331 …}
  -cartItem: App\Entity\Order\OrderItem {#106740
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#106765 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#106764 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8100
      #id: 3264
      #code: "IEEE00002187PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 9374
        #code: "IEEE00002187"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#183862 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751038212 {#7274
          date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1753969444 {#7322
          date: 2025-07-31 15:44: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: 32505
            #name: "IEEE 1471:2000"
            #slug: "ieee-1471-2000-ieee00002187-241026"
            #description: """
              New IEEE Standard - Superseded.<br />\n
              &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
              \t\t\t\t<br />\n
              The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
              An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
            -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 @1745791200 {#7317
          date: 2025-04-28 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 @971042400 {#7318
          date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1315519200 {#7316
          date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "1471"
        -bookCollection: ""
        -pageCount: 30
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8316 …}
      #position: 0
      #createdAt: DateTime @1751041156 {#7967
        date: 2025-06-27 18:19:16.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611970 {#8117
        date: 2025-08-19 15:59:30.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8260 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93314
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8100}
          #id: 3282
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8291 …}
      -apiLastModifiedAt: DateTime @1753740000 {#8099
        date: 2025-07-29 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-2519-0"
      -ean: "9780738125190"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/rTUrfT"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8128 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}
View Format same as normalized format

Submitted Data

This form was not submitted.

Passed Options

Option Passed Value Resolved Value
data 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106752
  -cart: App\Entity\Order\Order {#13331 …}
  -cartItem: App\Entity\Order\OrderItem {#106740
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#106765 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#106764 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8100
      #id: 3264
      #code: "IEEE00002187PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 9374
        #code: "IEEE00002187"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#183862 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751038212 {#7274
          date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1753969444 {#7322
          date: 2025-07-31 15:44: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: 32505
            #name: "IEEE 1471:2000"
            #slug: "ieee-1471-2000-ieee00002187-241026"
            #description: """
              New IEEE Standard - Superseded.<br />\n
              &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
              \t\t\t\t<br />\n
              The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
              An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
            -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 @1745791200 {#7317
          date: 2025-04-28 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 @971042400 {#7318
          date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1315519200 {#7316
          date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "1471"
        -bookCollection: ""
        -pageCount: 30
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8316 …}
      #position: 0
      #createdAt: DateTime @1751041156 {#7967
        date: 2025-06-27 18:19:16.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611970 {#8117
        date: 2025-08-19 15:59:30.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8260 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93314
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8100}
          #id: 3282
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8291 …}
      -apiLastModifiedAt: DateTime @1753740000 {#8099
        date: 2025-07-29 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-2519-0"
      -ean: "9780738125190"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/rTUrfT"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8128 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}
 same as passed value
product 
App\Entity\Product\Product {#7311
  #id: 9374
  #code: "IEEE00002187"
  #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
  #variants: Doctrine\ORM\PersistentCollection {#7744 …}
  #options: Doctrine\ORM\PersistentCollection {#7916
    #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
    #initialized: true
    -snapshot: [ …4]
    -owner: App\Entity\Product\Product {#7311}
    -association: [ …21]
    -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
    -backRefFieldName: null
    -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#183862 …}
    -isDirty: false
  }
  #associations: Doctrine\ORM\PersistentCollection {#7900 …}
  #createdAt: DateTime @1751038212 {#7274
    date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
  }
  #updatedAt: DateTime @1753969444 {#7322
    date: 2025-07-31 15:44: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: 32505
      #name: "IEEE 1471:2000"
      #slug: "ieee-1471-2000-ieee00002187-241026"
      #description: """
        New IEEE Standard - Superseded.<br />\n
        &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
        \t\t\t\t<br />\n
        The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
        An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
        """
      #metaKeywords: null
      #metaDescription: null
      #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
      -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 @1745791200 {#7317
    date: 2025-04-28 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 @971042400 {#7318
    date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
  }
  -releasedAt: null
  -confirmedAt: null
  -canceledAt: DateTime @1315519200 {#7316
    date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
  }
  -edition: null
  -coreDocument: "1471"
  -bookCollection: ""
  -pageCount: 30
  -documents: Doctrine\ORM\PersistentCollection {#7465 …}
  -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
}
 same as passed value

Resolved Options

Option Value
action 
""
allow_extra_fields 
false
allow_file_upload 
false
attr 
[]
attr_translation_parameters 
[]
auto_initialize 
true
block_name 
null
block_prefix 
null
by_reference 
true
compound 
true
constraints 
[]
csrf_field_name 
"_token"
csrf_message 
"The CSRF token is invalid. Please try to resubmit the form."
csrf_protection 
true
csrf_token_id 
null
csrf_token_manager 
Symfony\Component\Security\Csrf\CsrfTokenManager {#106772
  -generator: Symfony\Component\Security\Csrf\TokenGenerator\UriSafeTokenGenerator {#106773 …}
  -storage: Symfony\Component\Security\Csrf\TokenStorage\SessionTokenStorage {#106774 …}
  -namespace: Closure() {#106776 …}
}
data 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106752
  -cart: App\Entity\Order\Order {#13331 …}
  -cartItem: App\Entity\Order\OrderItem {#106740
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#106765 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#106764 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8100
      #id: 3264
      #code: "IEEE00002187PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 9374
        #code: "IEEE00002187"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#183862 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751038212 {#7274
          date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1753969444 {#7322
          date: 2025-07-31 15:44: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: 32505
            #name: "IEEE 1471:2000"
            #slug: "ieee-1471-2000-ieee00002187-241026"
            #description: """
              New IEEE Standard - Superseded.<br />\n
              &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
              \t\t\t\t<br />\n
              The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
              An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
            -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 @1745791200 {#7317
          date: 2025-04-28 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 @971042400 {#7318
          date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1315519200 {#7316
          date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "1471"
        -bookCollection: ""
        -pageCount: 30
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8316 …}
      #position: 0
      #createdAt: DateTime @1751041156 {#7967
        date: 2025-06-27 18:19:16.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611970 {#8117
        date: 2025-08-19 15:59:30.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8260 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93314
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8100}
          #id: 3282
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8291 …}
      -apiLastModifiedAt: DateTime @1753740000 {#8099
        date: 2025-07-29 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-2519-0"
      -ean: "9780738125190"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/rTUrfT"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8128 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}
data_class 
"Sylius\Bundle\OrderBundle\Controller\AddToCartCommand"
disabled 
false
empty_data 
Closure(FormInterface $form) {#106799
  class: "Symfony\Component\Form\Extension\Core\Type\FormType"
  use: {
    $class: "Sylius\Bundle\OrderBundle\Controller\AddToCartCommand"
  }
}
error_bubbling 
true
error_mapping 
[]
extra_fields_message 
"This form should not contain extra fields."
form_attr 
false
getter 
null
help 
null
help_attr 
[]
help_html 
false
help_translation_parameters 
[]
inherit_data 
false
invalid_message 
"This value is not valid."
invalid_message_parameters 
[]
is_empty_callback 
null
label 
null
label_attr 
[]
label_format 
null
label_html 
false
label_translation_parameters 
[]
mapped 
true
method 
"POST"
post_max_size_message 
"The uploaded file was too large. Please try to upload a smaller file."
priority 
0
product 
App\Entity\Product\Product {#7311
  #id: 9374
  #code: "IEEE00002187"
  #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
  #variants: Doctrine\ORM\PersistentCollection {#7744 …}
  #options: Doctrine\ORM\PersistentCollection {#7916
    #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
    #initialized: true
    -snapshot: [ …4]
    -owner: App\Entity\Product\Product {#7311}
    -association: [ …21]
    -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
    -backRefFieldName: null
    -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#183862 …}
    -isDirty: false
  }
  #associations: Doctrine\ORM\PersistentCollection {#7900 …}
  #createdAt: DateTime @1751038212 {#7274
    date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
  }
  #updatedAt: DateTime @1753969444 {#7322
    date: 2025-07-31 15:44: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: 32505
      #name: "IEEE 1471:2000"
      #slug: "ieee-1471-2000-ieee00002187-241026"
      #description: """
        New IEEE Standard - Superseded.<br />\n
        &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
        \t\t\t\t<br />\n
        The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
        An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
        """
      #metaKeywords: null
      #metaDescription: null
      #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
      -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 @1745791200 {#7317
    date: 2025-04-28 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 @971042400 {#7318
    date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
  }
  -releasedAt: null
  -confirmedAt: null
  -canceledAt: DateTime @1315519200 {#7316
    date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
  }
  -edition: null
  -coreDocument: "1471"
  -bookCollection: ""
  -pageCount: 30
  -documents: Doctrine\ORM\PersistentCollection {#7465 …}
  -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
}
property_path 
null
required 
true
row_attr 
[]
setter 
null
translation_domain 
null
trim 
true
upload_max_size_message 
Closure() {#106801
  class: "Symfony\Component\Form\Extension\Validator\Type\UploadValidatorExtension"
  use: {
    $translator: Symfony\Component\Translation\DataCollectorTranslator {#2251 …}
    $message: Closure() {#106800 …}
    $translationDomain: "validators"
  }
}
validation_groups 
[
  "sylius"
]

View Vars

Variable Value
action 
""
attr 
[]
attr_translation_parameters 
[]
block_prefixes 
[
  "form"
  "sylius_add_to_cart"
  "_sylius_add_to_cart"
]
cache_key 
"_sylius_add_to_cart_sylius_add_to_cart"
compound 
true
data 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106752
  -cart: App\Entity\Order\Order {#13331 …}
  -cartItem: App\Entity\Order\OrderItem {#106740
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#106765 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#106764 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8100
      #id: 3264
      #code: "IEEE00002187PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 9374
        #code: "IEEE00002187"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#183862 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751038212 {#7274
          date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1753969444 {#7322
          date: 2025-07-31 15:44: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: 32505
            #name: "IEEE 1471:2000"
            #slug: "ieee-1471-2000-ieee00002187-241026"
            #description: """
              New IEEE Standard - Superseded.<br />\n
              &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
              \t\t\t\t<br />\n
              The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
              An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
            -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 @1745791200 {#7317
          date: 2025-04-28 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 @971042400 {#7318
          date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1315519200 {#7316
          date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "1471"
        -bookCollection: ""
        -pageCount: 30
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8316 …}
      #position: 0
      #createdAt: DateTime @1751041156 {#7967
        date: 2025-06-27 18:19:16.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611970 {#8117
        date: 2025-08-19 15:59:30.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8260 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93314
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8100}
          #id: 3282
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8291 …}
      -apiLastModifiedAt: DateTime @1753740000 {#8099
        date: 2025-07-29 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-2519-0"
      -ean: "9780738125190"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/rTUrfT"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8128 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}
disabled 
false
errors 
Symfony\Component\Form\FormErrorIterator {#106822
  -form: Symfony\Component\Form\Form {#106831 …}
  -errors: []
}
form 
Symfony\Component\Form\FormView {#106802 …5}
full_name 
"sylius_add_to_cart"
help 
null
help_attr 
[]
help_html 
false
help_translation_parameters 
[]
id 
"sylius_add_to_cart"
label 
null
label_attr 
[]
label_format 
null
label_html 
false
label_translation_parameters 
[]
method 
"POST"
multipart 
false
name 
"sylius_add_to_cart"
priority 
0
required 
true
row_attr 
[]
submitted 
false
translation_domain 
null
unique_block_prefix 
"_sylius_add_to_cart"
valid 
true
value 
Sylius\Bundle\OrderBundle\Controller\AddToCartCommand {#106752
  -cart: App\Entity\Order\Order {#13331 …}
  -cartItem: App\Entity\Order\OrderItem {#106740
    #id: null
    #order: null
    #quantity: 1
    #unitPrice: 0
    #originalUnitPrice: 0
    #total: 0
    #immutable: false
    #units: Doctrine\Common\Collections\ArrayCollection {#106765 …}
    #unitsTotal: 0
    #adjustments: Doctrine\Common\Collections\ArrayCollection {#106764 …}
    #adjustmentsTotal: 0
    #version: 1
    #variant: App\Entity\Product\ProductVariant {#8100
      #id: 3264
      #code: "IEEE00002187PDF"
      #product: App\Entity\Product\Product {#7311
        #id: 9374
        #code: "IEEE00002187"
        #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
        #variants: Doctrine\ORM\PersistentCollection {#7744 …}
        #options: Doctrine\ORM\PersistentCollection {#7916
          #collection: Doctrine\Common\Collections\ArrayCollection {#7918 …}
          #initialized: true
          -snapshot: [ …4]
          -owner: App\Entity\Product\Product {#7311}
          -association: [ …21]
          -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
          -backRefFieldName: null
          -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#183862 …}
          -isDirty: false
        }
        #associations: Doctrine\ORM\PersistentCollection {#7900 …}
        #createdAt: DateTime @1751038212 {#7274
          date: 2025-06-27 17:30:12.0 Europe/Paris (+02:00)
        }
        #updatedAt: DateTime @1753969444 {#7322
          date: 2025-07-31 15:44: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: 32505
            #name: "IEEE 1471:2000"
            #slug: "ieee-1471-2000-ieee00002187-241026"
            #description: """
              New IEEE Standard - Superseded.<br />\n
              &quot; This recommended practice addresses the activities of the creation, analysis, and sus-tainment of architectures of software-intensive systems, and the recording of such architectures interms of architectural descriptions . A conceptual framework for architectural description is estab-lished. The content of an architectural description is defined. Annexes provide the rationale for keyconcepts and terminology, the relationships to other standards, and examples of usage. &quot;<br />\n
              \t\t\t\t<br />\n
              The purpose of this standard is to facilitate the expression and communication of architectures and thereby lay a foundation for quality and cost gains through standardization of elements and practices for architectural description. Despite significant efforts to improve engineering practices and technologies, software-intensive systems continue to present formidable risks and difficulties in their design, construction, deployment and evolution. Recent attempts to address these difficulties have focused on the earliest period of design decision-making and evaluation, increasingly referred to as the &quot;architectural level&quot; of system development. The phrases &quot;architectural level&quot; and &quot;architecture&quot; are widely, if imprecisely, used. Their use reflects acceptance of an architectural metaphor in the analysis and development of software-intensive systems. A key premise of this metaphor is that important decisions may be made early in system development in a manner similar to the early decision-making found in the civil architecture profession. Many innovations are resulting from this attention to the architectural level, among them architectural description languages and associated tools and environments, architectural frameworks, models and patterns, and techniques for architectural analysis, evaluation and architecture-based reuse. While these efforts differ considerably in important aspects, sufficient commonality exists to warrant the development of a recommended practice to codify their common elements. These innovations are occurring, and maturing, rapidly within many research and application communities, and they reflect differing interests, influences, insights, and intentions. There is a general consensus on the importance of the &quot;architectural level of systems development,&quot; and that that level consists of early decision-making about overall design structure, goals, requirements, and development strategies. However, there has not yet emerged any reliable consensus on a precise definition of a system's &quot;architecture,&quot; how it should be described, what uses such descriptions may serve, or where and when it should be defined. The boundaries and relationships between architectural trends and practices and other practices, and between architectural technology and other technology, are not yet widely recognized. In such situations, progress often depends on mediating influences. Potential adopters of architectural practices and technology need a frame of reference within which to address implementation and adoption decisions. Technology developers need a frame of reference within which to communicate the motivating concepts of their technology, and to accumulate and appreciate feedback from early adoption. To these ends, this standard is intended to reflect generally accepted trends in practices for architectural description and to provide a technical framework for further evolution in this area. Furtheremore, it establishes a conceptual framework of concepts and terms of reference within which future developments in system architectural technology can be deployed. This standard codifies those elements on which there is consensus; specifically the use of multiple views, reusable specifications for models within views, and the relation of architecture to system context.<br />\n
              An architectural description is used to communicate between client and developer to aid clarification of requirements and their impact on system design. The architectural description is developed in an evolutionary process from the expression of a system concept as a high level abstraction to one of a more detailed and tangible expression that is widely accepted as being an expression of design. An architectural description is used capture style and protocol standards that can be used to facilitate certain common attributes that promote system-to-system consistency.
              """
            #metaKeywords: null
            #metaDescription: null
            #shortDescription: "IEEE Recommended Practice for Architectural Description for Software-Intensive Systems"
            -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 @1745791200 {#7317
          date: 2025-04-28 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 @971042400 {#7318
          date: 2000-10-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -releasedAt: null
        -confirmedAt: null
        -canceledAt: DateTime @1315519200 {#7316
          date: 2011-09-09 00:00:00.0 Europe/Paris (+02:00)
        }
        -edition: null
        -coreDocument: "1471"
        -bookCollection: ""
        -pageCount: 30
        -documents: Doctrine\ORM\PersistentCollection {#7465 …}
        -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
      }
      #optionValues: Doctrine\ORM\PersistentCollection {#8316 …}
      #position: 0
      #createdAt: DateTime @1751041156 {#7967
        date: 2025-06-27 18:19:16.0 Europe/Paris (+02:00)
      }
      #updatedAt: DateTime @1755611970 {#8117
        date: 2025-08-19 15:59:30.0 Europe/Paris (+02:00)
      }
      #enabled: true
      #translations: Doctrine\ORM\PersistentCollection {#8260 …}
      #translationsCache: [
        "en_US" => App\Entity\Product\ProductVariantTranslation {#93314
          #locale: "en_US"
          #translatable: App\Entity\Product\ProductVariant {#8100}
          #id: 3282
          #name: null
          -shortDescription: null
          -description: null
          -notes: null
          -shippingInformation: "Instant download"
        }
      ]
      #currentLocale: "en_US"
      #currentTranslation: null
      #fallbackLocale: "en_US"
      #version: 9
      #onHold: 0
      #onHand: 0
      #tracked: false
      #weight: 0.0
      #width: null
      #height: null
      #depth: null
      #taxCategory: Proxies\__CG__\App\Entity\Taxation\TaxCategory {#8132 …}
      #shippingCategory: null
      #channelPricings: Doctrine\ORM\PersistentCollection {#8294 …}
      #shippingRequired: true
      #images: Doctrine\ORM\PersistentCollection {#8291 …}
      -apiLastModifiedAt: DateTime @1753740000 {#8099
        date: 2025-07-29 00:00:00.0 Europe/Paris (+02:00)
      }
      -publishedAt: null
      -isbn: "978-0-7381-2519-0"
      -ean: "9780738125190"
      -numberOfUsers: 1
      -physicalProduct: false
      -downloadableImmediately: true
      -downloadable: true
      -drmViewerUrl: "https://online-viewer.normadoc.com/rTUrfT"
      -sellable: true
      -documents: Doctrine\ORM\PersistentCollection {#8128 …}
      -drmTokens: Doctrine\ORM\PersistentCollection {#8120 …}
      -enabledForSubscribers: true
      -currentAreaContext: null
    }
    #productName: null
    #variantName: null
  }
}