ISSUE-132: Guide for copy/paste Twig extension #152
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@DiegoPino @alliomeria @karomabiles Let me know if any of this doesn't make sense. Also, I guess this should target 1.1.0 now since the copy/paste changes were merged there? Should we start that branch/version the docs pages? |
|
Oh.. 1.1.0 Right. good, very good question. Ok, let me check/read the docs first. Keep the current pull to 1.0.0 open. Will get back to you tomorrow with the Docs 1.10 updates/idea... Thanks so much! |
|
@aksm cool. Let me talk to @alliomeria about the new tag here. Time to move into 1.1.0 branch but not make it the default yet. More today! |
|
Ok, this reads better. Let's merge into 1.1.0! Thanks @aksm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #132.
Includes Twig filters and functions we provide for completeness, references to Symfony's built-in extensions, and references (tested that they're actually available) to the Drupal-specific extensions.
This is a simplified re-do of #133 and excludes the reference/link to #151, which we can add back in that PR.