Add option to format or remove 'extra space that salesforce adds to apex tags' in VF pages.

[Justin Julicher]

If you create a visualforce page like the following:

‌

save it, then retrieve it the output will be:

‌

notice the extra space after the opening bracket?

Granted on small files like this it’s not an issue but when dealing with a large file it can be a little bit of a pain when using version control as this would show differences.

‌

Could we have an option to either

• remove spaces on retrieval on opening brackets.
• when formatting/creating brackets add a space in.

The behaviour exists whenever a page is saved (dev console, editor, API etc).

Of course, we queried SF about it and got the WAD response.

‌

thanks

[Scott Wells]

Issue tracker grooming. Yeah, this drives me kind of crazy...as does any change that Salesforce makes to successfully deployed metadata when retrieving it from the exact same org. They shouldn't do that.

Having said that, the only changes that IC2 makes right now to retrieved metadata are to fix truly broken retrieved metadata, e.g., *.installedPackage files which include an invalid activateRSS element. I don't think that changing other files' contents -- even just simple whitespace in markup -- would be a good idea because there's no way to know when it's intentional and when it's not.

You can, of course, use retrieval substitution rules to accomplish the goal.