Reply 59

https://twitter.com/MarcDrummond/status/1295443336694767616

Hi Marc! Yes, that article is for PL Node. It was decided to not develop PL PHP any more, so I have moved to PL Node and haven't really properly tested PL PHP with D9. I wrote a blog post about moving to PL Node some time ago: https://www.aleksip.net/a-new-approach-for-a-new-pattern-lab

Comments

If the required changes are implemented in PL Node core, I would definitely have a go at writing a Node version of DTP. Maybe you would like to voice your support and leave a comment in the PL Node core issue? 😊

Submitted by Mario Hernandez on 19 August 2020

Permalink

hey @MarcDrummond we've been using Pattern lab Node in production for a while. No really problems at all. In fact, I recently upgraded PL to use Twig 2.0 so it works with D9 and so far so good. I wish we could include pseudo patterns, but for us it hasn't been an issue

Submitted by Marc Drummond on 19 August 2020

Permalink

Dang, was looking at the node documentation and seeing that when patterns are included at higher levels, the data for that pattern is not carried along with it, that's pretty rough. Duplicating all that data at each level is thorny. patternlab.io/docs/creating-…

Submitted by Mario Hernandez on 19 August 2020

Permalink

Recreate the data? My typical workflow is creating a data file for each component. However, sometimes it makes sense to use data.json. It all depends.

Submitted by Marc Drummond on 19 August 2020

Permalink

Oof, you also can't include pseudo-patterns when doing includes in the node-based Pattern Lab? That's been the secret sauce for me. Pseudo-patterns with variations of data, then using those at higher levels. patternlab.io/docs/creating-…

Add new comment

The content of this field is kept private and will not be shown publicly.
This must be an external URL such as https://example.com.