Skip to content
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

FrameworkBundle Configuration -> bad documentation for assets #6146

Closed
poolerMF opened this issue Jan 14, 2016 · 0 comments
Closed

FrameworkBundle Configuration -> bad documentation for assets #6146

poolerMF opened this issue Jan 14, 2016 · 0 comments
Labels
actionable Clear and specific issues ready for anyone to take them.

Comments

@poolerMF
Copy link

http://symfony.com/doc/current/reference/configuration/framework.html

I install SF3 .. in config.yml I see:

templating:
    engines: ['twig']
    #assets_version: SomeVersionScheme

when I uncomment assets_version ... I'm getting error:

Unrecognized option "assets_version" under "framework.templating"

In code I see that assets parameters moved under framework.assets .. documentation should by updated and template code for config.yml too

@xabbuh xabbuh added the actionable Clear and specific issues ready for anyone to take them. label Jan 14, 2016
weaverryan added a commit that referenced this issue Feb 21, 2016
…nd add base_path documentation (snoek09)

This PR was merged into the 2.7 branch.

Discussion
----------

move assets options from templating to assets section and add base_path documentation

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | 2.7
| Fixed tickets | #6146

Commits
-------

2a905d8 small fixes for xml configuration examples
5d06eb5 document base_path option
cc12d7f change order of assets configuration options
61403e7 remove unused reference
5969b80 move packages and base_urls to assets section remove templating config from examples put anchor back
46156f4 put anchor back
cd0efed [WIP] moving assets version and version_format options under assets section
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actionable Clear and specific issues ready for anyone to take them.
Projects
None yet
Development

No branches or pull requests

3 participants