WordPress.org

Make WordPress Core

Opened 2 months ago

Closed 2 months ago

#41073 closed defect (bug) (duplicate)

Introduce linting for code editor

Reported by: karmatosed Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Themes Keywords:
Focuses: Cc:

Description

Consider adding this just like plugins.

Change History (7)

#1 @karmatosed
2 months ago

  • Summary changed from Code linting for theme editing via code editor to Introduce linting for code editor

#2 @swissspidy
2 months ago

I think that's actually a duplicate of #12839. It was also discussed during the summit that it should finally get implemented. That ticket has been open for 7 years now.

#3 @ahortin
2 months ago

@swissspidy Can you pelase explain why something like this and ticket #12423 are more of a priority than #9757, which has also been waiting more than 8 years for actioning. WordPress is first and foremost a cms, not a code editor. I'm confident in saying that more people want to be able to upload a zip to replace an existing plugin/theme, than wanting to be able to edit plugin/theme code.

If you want to edit plugin/theme files, use a proper editor/development environment. After editing your code, wouldn't it be great if you could then zip up your updated plugin/theme files and then upload it within the dashboard to replace an existing plugin/theme!

#4 @swissspidy
2 months ago

@ahortin I guess this ticket was opened in response to https://make.wordpress.org/core/2017/06/16/4-9-and-gutenberg/, which was just published the other day.

In the meantime I think we can do another user-focused 4.9 release with the theme of editing code and managing plugins and themes, doing v2s and polishing some features we brought into WP last year.

Sounds like #9757 might fall under that, too! Again, I didn't say it's something that will never be implemented. If someone (you, me, anybody) can step up and contribute to that, they are more than welcome to do so. It's just so that nothing happened after the initial patch on that ticket.

#5 @ahortin
2 months ago

@swissspidy Thanks for the clarification :-)

This ticket was mentioned in Slack in #design by melchoyce. View the logs.


2 months ago

#7 @melchoyce
2 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Closing in favor of #12839.

Note: See TracTickets for help on using tickets.