-
Notifications
You must be signed in to change notification settings - Fork 62
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
Mega PR: Merging Drupal Pattern Lab Fork Back Into Main Pattern Lab PHP Core #129
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
Remove extra character from InstallerUtil so dev branch works
… comments to explain my PHP chicken scratch. Addresses existing open issue #3 and corresponds with the 2nd half of work mentioned in drupal-pattern-lab/patternengine-php-twig#1
Updating global data to use `yml` or `yaml`
v2.8.0 RC - Merging Latest on Dev into Master
This reverts commit 8a51a73.
This reverts commit 505f32c.
Replace possible dots in pattern names with dashes
…-lineages Fix for Broken Lineage Functionality in PL When Using Twig templates w/ Path Namespaces (ie. Drupal 8-friendly Paths)
Don't overwrite nameClean if it has already been set
…exist when scanning the pattern source directory for patterns; adds the RecursiveIteratorIterator flag to follow symbolic links while still continuing to skip dots (. and ..). This opens the door for some creative workarounds to the rigid way Pattern Lab expects pattern templates to be organized at the file system level + how the physical path to a pattern determines how it's organized in Pattern Lab... pattern-lab#28
Allow Pattern Lab to follow pattern symlinks when registering patterns
… Default files in the public dir if entire directory gets wiped. Solves #14
…ic-dir Working solution to regenerate missing styleguideKit index.html in the public directory
Chore as part of mega merge back into the main PL mothership repo
@EvanLovely @aleksip could one of you guys check this out when you get a chance? I know we're going to need do another pass through reviewing the existing issue queue after this goes out the door to make sure we're not missing anything however this should be pretty darn close otherwise. LMK! |
🎉 |
This was referenced Nov 5, 2017
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.
Placeholder Mega PR per the awesome conversation @EvanLovely and I had earlier today.
This folds in the past 5 months worth of maintenance and enhancement updates made to the Drupal Pattern Lab working group's ongoing Pattern Lab PHP Core fork as part of the new exciting updates @bradfrost posted about earlier this week!
Changelog
yml
oryaml
which addresses Default data files only support .yaml extension, while pattern-specific data file allow .yml #93 and Ensure YAML data files can use yml extension too #96 | @EvanLovelyNext Up (Fast Follows)
Bug Fixes & Maintainance
Better Installation / Setup Process
Better Markdown Docs
Pattern Lab Customization / Configuration
Soon After (@todo: finish reviewing remaining open issues following next release)
TODOs