티스토리 수익 글 보기

티스토리 수익 글 보기

Comments on: JavaScript Chat Agenda for May 16th https://make.wordpress.org/core/2017/05/15/javascript-chat-agenda-for-may-16th/ WordPress Development Updates Tue, 16 May 2017 12:48:02 +0000 hourly 1 https://wordpress.org/?v=7.0-alpha-61499 By: Stephen Edgar https://make.wordpress.org/core/2017/05/15/javascript-chat-agenda-for-may-16th/#comment-32455 Tue, 16 May 2017 12:48:02 +0000 https://make.wordpress.org/core/?p=22104#comment-32455 <ul> <li> Gutenberg is currently using the ESLint config <code>eslint-config-wordpress</code> and also using some additional ESLint rules and possibly overriding others that are not currently included in <code>eslint-config-wordpress</code>, these should be audited against both the current <a href="https://make.wordpress.org/core/handbook/best-practices/coding-standards/javascript/">JavaScript coding standards</a> and <code>eslint-config-wordpress</code>. </li> <li> The <code>eslint-config-wordpress</code> project is now under the WordPress Coding Standards repo alongside the PHPCS PHP sniffs at https://github.com/WordPress-Coding-Standards/eslint-config-wordpress. </li> <li> The <em>semantic versioning</em> based roadmap for <code>eslint-config-wordpress</code> is <a href="https://github.com/WordPress-Coding-Standards/eslint-config-wordpress/issues/8" rel="nofollow">here</a>. </li> <li> A second ESLint repo <code>eslint-plugin-wordpress</code> is the <em>ESLint shared plugin</em> version for WordPress https://github.com/WordPress-Coding-Standards/eslint-plugin-wordpress, this <code>eslint-plugin-wordpress</code> shared plugin config has a few goals: <ul> <li> If WordPress or a WordPress project requires custom ESLint rules to be written this is where they should be created (none currently exist at this time). </li> <li> To make available to <code>eslint-config-wordpress</code> custom ESLint configs for use with WordPress such as QUnit and JSDoc ESLint plugins and configs configured for WordPress' use case. </li> </ul> <li> Lastly the core ticket proposing to add ESlint here: <a href="https://core.trac.wordpress.org/ticket/31823" rel="nofollow">#31823</a> </li> </ul> I'm sure I've forgotten to mention a ton of things, but I'll get this posted now as scheduled to start in ~10 minutes from now in #core on Slack]]> Hey, @netweb here with my “build tools” component maintainer hat on 👷

  • Gutenberg is currently using the ESLint config eslint-config-wordpress and also using some additional ESLint rules and possibly overriding others that are not currently included in eslint-config-wordpress, these should be audited against both the current JavaScript coding standards and eslint-config-wordpress.
  • The eslint-config-wordpress project is now under the WordPress Coding Standards repo alongside the PHPCS PHP sniffs at https://github.com/WordPress-Coding-Standards/eslint-config-wordpress.
  • The semantic versioning based roadmap for eslint-config-wordpress is here.
  • A second ESLint repo eslint-plugin-wordpress is the ESLint shared plugin version for WordPress https://github.com/WordPress-Coding-Standards/eslint-plugin-wordpress, this eslint-plugin-wordpress shared plugin config has a few goals:

    • If WordPress or a WordPress project requires custom ESLint rules to be written this is where they should be created (none currently exist at this time).
    • To make available to eslint-config-wordpress custom ESLint configs for use with WordPress such as QUnit and JSDoc ESLint plugins and configs configured for WordPress’ use case.
  • Lastly the core ticket proposing to add ESlint here: #31823

I’m sure I’ve forgotten to mention a ton of things, but I’ll get this posted now as scheduled to start in ~10 minutes from now in #core on Slack

]]>