Skip to content

[FrameworkBundle] Set default public directory on install assets #23513

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

Closed
wants to merge 2 commits into from

Conversation

yceruto
Copy link
Member

@yceruto yceruto commented Jul 14, 2017

Q A
Branch? 3.3
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets -
License MIT
Doc PR -

After symfony/flex#122 and symfony/recipes#106 the default directory to install assets is public.

@xabbuh
Copy link
Member

xabbuh commented Jul 15, 2017

This will break applications that are using the old directory structure and just update their dependencies using composer update.

@yceruto
Copy link
Member Author

yceruto commented Jul 15, 2017

@xabbuh right, but this is about default value for default directory structure 4.0, still you can use the target argument for old structures, no? or this kind of BC break is not allowed for 4.0?

@yceruto yceruto changed the title [FrameworkBundle] Fix default public directory on install assets [FrameworkBundle] Set default public directory on install assets Jul 15, 2017
@yceruto
Copy link
Member Author

yceruto commented Jul 15, 2017

Upgrade note added.

But still I'm not sure if we should add a warning messages on 3.4 on assets:install, WDYT?

@ro0NL
Copy link
Contributor

ro0NL commented Jul 15, 2017

4.0 can provide the target path as well ;-) it's not like we must update on this side.

It does makes sense though :) however you need to trigger a deprecation in 3.4 first (if the argument is not given) i guess.

@fabpot
Copy link
Member

fabpot commented Jul 16, 2017

What about doing something similar to what I did in #23535?

@yceruto yceruto changed the base branch from master to 3.3 July 16, 2017 14:15
@yceruto
Copy link
Member Author

yceruto commented Jul 16, 2017

@fabpot I've rebased to 3.3 base branch as a bugfix, also added BC for web directory :) thanks!

@nicolas-grekas nicolas-grekas added this to the 3.3 milestone Jul 17, 2017
UPGRADE-4.0.md Outdated
@@ -223,6 +223,8 @@ Form
FrameworkBundle
---------------

* The `assets:install` command does not install assets into `web` directory by default, but into `public` directory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not true anymore. It will install under public or web.

@fabpot
Copy link
Member

fabpot commented Jul 17, 2017

Thank you @yceruto.

fabpot added a commit that referenced this pull request Jul 17, 2017
…assets (yceruto)

This PR was squashed before being merged into the 3.3 branch (closes #23513).

Discussion
----------

[FrameworkBundle] Set default public directory on install assets

| Q             | A
| ------------- | ---
| Branch?       | 3.3
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | -
| License       | MIT
| Doc PR        | -

After symfony/flex#122 and symfony/recipes#106 the default directory to install assets is `public`.

Commits
-------

1bdfe0b [FrameworkBundle] Set default public directory on install assets
@fabpot fabpot closed this Jul 17, 2017
@yceruto yceruto deleted the web2public branch July 17, 2017 11:53
@fabpot fabpot mentioned this pull request Jul 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants