Skip to content
This repository has been archived by the owner on May 18, 2022. It is now read-only.

#_ is deprecated #152

Open
Toddses opened this issue Apr 17, 2015 · 6 comments
Open

#_ is deprecated #152

Toddses opened this issue Apr 17, 2015 · 6 comments
Labels

Comments

@Toddses
Copy link
Collaborator

Toddses commented Apr 17, 2015

Get this warning when running YeoPress with the latest version of yeoman-generator (0.19.1)

(!) #_ is deprecated. Require your own version of Lodash or underscore.string
@Toddses Toddses added bug and removed bug labels Apr 17, 2015
@wesleytodd
Copy link
Owner

yeoman/generator#766

Looks like our new release will need this fix as well.

@wesleytodd
Copy link
Owner

This is actually a much bigger problem than I thought. The fs refactor is causing internal wordpress files to be parsed as templates, specifically this one: https://core.trac.wordpress.org/browser/tags/4.1.1/src/wp-includes/class-wp-customize-widgets.php#L708

So this is actually mangling wp functionality.

I dont have time to work on this right now, but if you want to, all we need to do is make that one call NOT do template parsing.

@wesleytodd
Copy link
Owner

and fwiw, i pushed an error log and a beta tag in package.json so if we get this fixed we can publish a beta with the fixes.

@wesleytodd wesleytodd added the bug label Apr 19, 2015
This was referenced Apr 19, 2015
@Vivekbhusal
Copy link

is there any update on for this issue? i am trying to generate wordpress-plugin using wp-make. Is there any work around or patches?

@Toddses
Copy link
Collaborator Author

Toddses commented Jul 8, 2015

Not really atm. Time has been an issue for me lately, as I'm sure for Wes as well. If someone can issue a valid pull request I am sure we will pull it in.

That said I have still been using YeoPress with this deprecation warning and have had no issues myself.

@wesleytodd
Copy link
Owner

^^ what he said :)

Also I am not sure where wp-make comes in here, are you trying to switch to yeopress? If so this issue shouldn't actually break anything, we just need to fix it before it is actually removed from yeoman.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants