value: '<%= pkg.version %>' will results in Parse error: syntax error, unexpected T_DNUMBER in php;

if I use value: '"<%= pkg.version %>"' (ie. putting quote inside), then it works initially, on next update it insert another pair of quotes which breaks it.

It would be a better to just let user specify the type of variable? so the tool know whether to wrap it in quotes or not.

Support for class constants in addition to constants declared using define()

I would like to use the following in my Gruntfile.js

grunt.initConfig({
setPHPConstant: {
      example: {
          constant    : 'TEST',
          value       : 'stage-<%= grunt.template.today("yyyy-mm-dd") %>',
          file        : 'test.php'
      }
  },
});

to update the following code in test.php

class A {
  const TEST = 'replace this';
}

I'm posting this issue to let you know that we will be publishing Grunt 0.4 on Monday, February 18th.

If your plugin is not already Grunt 0.4 compatible, would you please consider updating it? For an overview of what's changed, please see our migration guide.

If you'd like to develop against the final version of Grunt before Monday, please specify "grunt": "0.4.0rc8" as a devDependency in your project. After Monday's release, you'll be able to use "grunt": "~0.4.0" to actually publish your plugin. If you depend on any plugins from the grunt-contrib series, please see our list of release candidates for compatible versions. All of these will be updated to final status when Grunt 0.4 is published.

Also, in an effort to reduce duplication of effort and fragmentation in the developer community, could you review the grunt-contrib series of plugins to see if any of your functionality overlaps significantly with them? Grunt-contrib is community maintained with 40+ contributors—we'd love to discuss any additions you'd like to make.

Finally, we're working on a new task format that doesn't depend on Grunt: it's called node-task. Once this is complete, there will be one more conversion, and then we'll never ask you to upgrade your plugins to support our changes again. Until that happens, thanks for bearing with us!

If you have any questions about how to proceed, please respond here, or join us in #grunt on irc.freenode.net.

Thanks, we really appreciate your work!

For example

define('ENV','other "env"');

would not work as expected... There are several other problems with the regex relating to mixing quote mark types.

Update the regex to us \1 style back back references to store the type of regex we are inside, and remember to check for escaped quote marks of that type and ignore them.

For example

define("CACHE_BUSTING_REVISION", "");

Task used

grunt.initConfig({
    setPHPConstant: {
        stage: {
            constant: 'CACHE_BUSTING_REVISION',
            value: '<%= grunt.template.today("yyyymmddhh") %>',
            file: 'config/application.inc.php'
        }
    }
});

grunt.loadNpmTasks('grunt-php-set-constant');

grunt.registerTask('cachebust', 'setPHPConstant');

Line isn't updated when running grunt task.

It works when I set the initial value to 0 tho, so I can deal with that, but would be great if it would work with an empty string!

Thanks for the work by the way, extremely useful!

Example:
When trying to swap out value for DB_USER I noticed a problem if the constant is left empty. This code works:

File value

define('DB_USER', 'temp_user');

Grunt config

setPHPConstant : {

                DB_USER : {
                    constant : 'DB_USER',
                    value    : 'real_value',
                    file     : {path to file}
                }

Changing the define from:

define('DB_USER', 'temp_user');

to:

define('DB_USER', '');

Will result in the task not adding the 'real_value' of the constant.

The plugin does its job very well. The only issue I am facing is related to the removal of the tab before the constant when the constant is indented.

Can you please let me know if I am doing something wrong at my end or is it a known issue?

Try something like:

("([^\\"]|\\.)*"|'([^\\']|\\.)*')

from http://blog.stevenlevithan.com/archives/match-quoted-string

But. W single quotes different