Update to API v39.0

[rmccu]

How can I contribute changes back for upgrading to API v39.0?

[rmccu]

Hmm, I tried to regenerate and the Apex class is getting larger than 1mb of content. I have some ideas for how to reduce this. How can I contribute those back?

[afawcett]

@rmccu Ah i guess this was always on the cards as an issue, hitting 1mb limit. The instructions for regenerating are in the readme file below. It involves running the patcher tool, thats my go to approach for implementing repeatable upgrades in reasonably short order. Its going to be tough i guess to do this in a backwards compatible way since the types are all inner classes and qualified by the outer. It maybe that for 39 onwards a new class is needed to allow it to sit alongside the old and allow folks to migrate code bit by bit? Whats your thoughts?

[rmccu]

I made significant changes to the patcher and it now works with v40 and some of v41 new metadata classes and generates an Apex class that is ~830k in size. There were 2 big changes that made a significant difference in the size of the generated Apex code:

• Add private static final String NS = 'http://soap.sforce.com/2006/04/metadata'; to the MetadataService class and use that variable in place of the URL everywhere
• Replace 4 x space with tab (4 bytes/characters into 1)

Here is the updated MetadataServicePatcher:MetadataServicePatcher.txt

[afawcett]

@rmccu thanks so much for this! I'll take a look next week.

[rmccu]

No problem @afawcett, glad I could make a contribution.