Flesh out broccoli-css-blocks plugin.
#87
Conversation
|
|
||
| return this.analyzer; | ||
| // Write our compiled CSS to the output tree. | ||
| // QUESTION: GUH! TOM! THIS DOESN'T APPEAR IN THE OUTPUT TREE! |
There was a problem hiding this comment.
This is the biggest problem that I don't quite understand 🙂
I'm trying to write the compiled CSS file out to the source tree, and I can see it in CSS Blocks' output tmp directory, but by the time the final project is dumped out to /dist it disappears again. I'm assuming I'm just not placing it in the correct spot in the output tree. Any insight?
| // We're just analyzing right now. | ||
| let files = await readdirAsync(this.inputPaths[0]); | ||
| // This build step is *mostly* just a pass-through of all files! | ||
| // QUESTION: Tom, is there a better way to do this in Broccoli? |
There was a problem hiding this comment.
Aka, "hey broccoli, recursively symlink every file for me, but make sure the directories are all real so I'm not editing someone else's output tree by accident – or worse, the source files!
| let styleMapping = new StyleMapping<"Opticss.Template">(optimized.styleMapping, blocks, options, this.analyzer.analyses()); | ||
|
|
||
| // Attach all computed data to our magic shared memory transport object... | ||
| this.transport.mapping = styleMapping; |
There was a problem hiding this comment.
This is all hand-wave-y shared state between Rewriters and Analyzers. Chris and I are still settling on a proper way to handle this for all build types – this is in a "just get it to work" state and will be cleaned up before landing.
|
Superseded by #90 |
Still a number of outstanding QUESTIONs and TODOs. See code comments for details.