-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow denormalization to simple array #91
Comments
What about I'm curious about use-cases for specifically having arrays instead of objects, but just for the convenience stuff, this trick might be enough and still keeps a proper unique, discoverable and auto-completable identifier with the FQCN. It may require us to provide a small custom denormalizer for Depending on what are the benefits you really expect with this idea, we can also generate on fly such generic classes for an identifier. |
POC for StenopePHP/Stenope#91 (comment) Such content pages allows any properties by relying on \stdClass specificities. It just need creating once a class extending \stdClass. Then, any content, with various and different properties can be loaded with the content manager with its slug: ```php $manager->getContent(Misc::class, 'elaomojis') ```
POC for StenopePHP/Stenope#91 (comment) Such content pages allows any properties by relying on \stdClass specificities. It just need creating once a class extending \stdClass. Then, any content, with various and different properties can be loaded with the content manager with its slug: ```php $manager->getContent(Misc::class, 'elaomojis') ```
POC for StenopePHP/Stenope#91 (comment) Such content pages allows any properties by relying on \stdClass specificities. It just need creating once a class extending \stdClass. Then, any content, with various and different properties can be loaded with the content manager with its slug: ```php $manager->getContent(Misc::class, 'elaomojis') ```
For some usage, or just for convenience, it might be interesting to skip the "Create a Model" phase and juste get object as array to be manipulated in twig.
A unique key like
user
would be used instead of a FQCN:$contentManager->getContents('user');
We would need to consider any unwanted side-effect.
The text was updated successfully, but these errors were encountered: