Skip to content

Add example and docs to only enqueue when required #6

@tripflex

Description

@tripflex

Good tutorial, one thing I would like to mention (and I see it mentioned in the README), is to provide more details and example to show users how to only enqueue their script or style on THEIR pages (or pages required).

Being a full time WordPress developer, my biggest gripe about inexperienced or sloppy developers is enqueuing a script/style on every single page ... which I deal with constantly when there are javascript errors in their code or they add a dependency that conflicts with my plugins.

I literally have a function in all my plugins called death_to_sloppy_devs() to dequeue scripts/styles ... the list is up to 40 plugins now 😮

If I can find some time next week i'll submit a PR for you, just wanted to mention it while I was checking this out, as I honestly think it's not laziness, it's just not being experienced enough or even knowing how to do it correctly.

Even created this repo years ago that I never ended updating, but now reminds me I should finish it 😛 https://github.com/tripflex/dequeue-sloppy-devs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions