Skip to content

Conversation

@illepic
Copy link
Contributor

@illepic illepic commented Oct 26, 2020

No description provided.

@illepic illepic requested a review from a team October 26, 2020 18:35
Drupal: true,
jQuery: true,
_: true,
// _: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this intentional?

Copy link
Contributor

@jryanconklin jryanconklin left a comment

Choose a reason for hiding this comment

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

There’s an empty spacing.json file. Beyond that it’s worth noting this approach will break Octane scripts, which now is configured to separate the theme, module, and particle into separate directories. Considering the priority of the Octane project, I wouldn’t expect this to be changed until the New Year.

path: APP_DIST,
publicPath: APP_DIST_PUBLIC,
// Output all CSS/JS/images/twig to dist/ within drupal theme
path: path.resolve(__dirname, 'particle_theme/dist'),
Copy link
Contributor

Choose a reason for hiding this comment

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

Octane programmatically moves this directory.

const { NODE_ENV, PARTICLE_PL_HOST = '' } = process.env;
// Constants: root
const { PATTERN_LAB_DIST } = require('../../particle.root.config');
const { PATH_DIST } = require('../../particle.root.config');
Copy link
Contributor

Choose a reason for hiding this comment

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

Are we undoing having particle split out from the Drupal theme?

module.exports = ({ options, env }) => {
const tailWindPath = path.resolve(
__dirname,
'./source/default/tailwind.config.js'
Copy link
Contributor

Choose a reason for hiding this comment

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

This might be nice to set up as config since default may not survive as a name.

},
variants: {},
plugins: [tailwindCustomForms],
future: {
Copy link
Contributor

Choose a reason for hiding this comment

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

Might be worth a comment here that future can be removed in Tailwind 2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants