Skip to content

Updating {% block javascripts position to match recipe change #14836

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

Merged

Conversation

weaverryan
Copy link
Member

Hi!

See symfony/recipes#874

I did this against 4.4 (which is normally done for bug fixes) because this would appear as a "documentation bug" if we updated the recipe but didn't update the docs.

Thanks!

@carsonbot carsonbot added this to the 4.4 milestone Jan 15, 2021

The ``encore_entry_link_tags()`` comes from WebpackEncoreBundle and relies
on a feature in Encore that was first introduced in version 0.21.0. Previously,
the ``asset()`` function was used to point directly to the file.
Copy link
Member Author

Choose a reason for hiding this comment

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

The old note had probably been there long enough - so I just replaced it with the new one

@weaverryan weaverryan force-pushed the changing-javascripts-block-position branch from c6e7b91 to 8c2c794 Compare January 15, 2021 19:42
@weaverryan weaverryan changed the title [WCM] Updating {% block javascripts position to match recipe change Updating {% block javascripts position to match recipe change Jan 15, 2021
@weaverryan
Copy link
Member Author

This is now ready!

@javiereguiluz
Copy link
Member

I like this change Ryan! And the needed doc changes are small, so the transition will be smooth. Thanks!

@javiereguiluz javiereguiluz merged commit f6cf126 into symfony:4.4 Jan 17, 2021
@weaverryan weaverryan deleted the changing-javascripts-block-position branch January 18, 2021 00:36
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.

4 participants