Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-implementation of Apex client code gen #698

Merged
merged 1 commit into from
Jul 31, 2018

Conversation

muenzpraeger
Copy link
Contributor

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
  • Filed the PR against the correct branch: master, 4.0.x. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

Re-implementation of Apex client library, finalized TODOs from PR #692

@wing328

@wing328
Copy link
Member

wing328 commented Jul 31, 2018

@muenzpraeger the change looks good to me (but I'm no expert in Apex)

@wing328
Copy link
Member

wing328 commented Jul 31, 2018

@muenzpraeger can you please share with me how to perform a compile test for the Apex Petstore client?

We can then set that up in the CI to ensure the client compiles after changes to Apex generator or templates.

@muenzpraeger
Copy link
Contributor Author

The compile would need an active Salesforce environment, as the compile happens in cloud, not locally.

@muenzpraeger
Copy link
Contributor Author

The source would need to be pushed to an ephemeral environment, like in this config:

https://github.com/trailheadapps/easy-spaces/blob/b74d3dbaa7b2e3ff59af46185fd3c81a8df90b32/.circleci/config.yml#L73

@wing328
Copy link
Member

wing328 commented Jul 31, 2018

For the CI setup, let's work on that later.

If no further question/feedback, I'll merge this into master in an hour or so.

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

Successfully merging this pull request may close these issues.

2 participants