Download the PHP package nzour/symfony-advanced-resolving without Composer
On this page you can find all versions of the php package nzour/symfony-advanced-resolving. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package symfony-advanced-resolving
Symfony advanced resolving
Requirements
- php >= 8.0
- symfony >= 5.3
Installation
Important: Make sure bundle \AdvancedResolving\AdvancedResolvingBundle become enabled, otherwise enable it in bundles.php
Examples
1 Using #[FromQuery] attribute:
GET {host}/foo?value={value}
2 Using #[FromQuery] attribute with different param name:
GET {host}/foo?foobar={value}&score={score}
3 Using #[FromQuery] with class typehint
GET {host}/foo?value={value}&score={score}
Note: it's not possible to rename properties of FooQuery via additional attributes
4 Using #[FromBody]
Docs
Feature based on Symfony's ArgumentValueResolver flow, therefore make sure your controllers tagged with controller.service_arguments or marked via #[AsController] attribute.
Built in
bin/console debug:meta-resolvers- View list of defined meta resolvers-
FromBody
Implementation class FromBodyMetaResolver
Uses symfony serializer to instantiate objects from plain data, default format of data is json. There is a way to specify another format:
#[FromBody(format: XmlEncoder::FORMAT)]. It is not possible to change format globally. -
FromQuery
Implementation class FromQueryMetaResolver
You can specify different param name
#[FromQuery(paramName: 'foobar')]Parameter FromQuery::$disableTypeEnforcement is responsible for flag AbstractObjectNormalizer::DISABLE_TYPE_ENFORCEMENT when resolve object. It's value true by default.
Not implemented yet
- FromHeader
- FromForm
Errors
- Symfony Serializer's Exceptions
- NonNullableArgumentWithNoDefaultValueFromQueryParamsException - Only for #[FromQuery]. Argument is not nullable, has no default value and there is also no value specified from request
- CouldNotCreateInstanceFromQueryParamsException - Just like above, but if argument's typehint is class
Extend by user land
If you want to create your own attribute and algoritm that resolves it, follow steps:
- Define your attribute or use existing attribute
- Define class-service, that implements MetaResolverInterface
- Method supportedAttribute should return class-string of which attribute it supports
- Mark your service with tag
meta-resolver
Limitations
- Built in resolvers work with Symfony Serializer
- No interop with Symfony Validator (yet, or maybe not yet)
-
Built in attributes work only with endpoint's parameters, it's not possible to combine attributes:
The entire class FooDto would be compiled from Body parameters.
However property FooDto::$foobar is marked with attribute #[FromQuery], resolver would not try to find parameter foobar inside query-parameters and try set it as property's value.
