-
Notifications
You must be signed in to change notification settings - Fork 33
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
Create arbitrary SObjects from Map #9
base: master
Are you sure you want to change the base?
Conversation
|> create_sobject(name, map) | ||
end | ||
def create_sobject(client, name, map) do | ||
Forcex.post("/services/data/v20.0/sobjects/#{name}", map, client) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeffweiss curious why you chose to have Forcex module methods use a trailing client
param rather than leading (for pipeline operator)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sebbean the reason that I have client
as the trailing param is that for most of the calls, it is the least relevant to the name of the function. True, moving client
to the first parameter would make it more cases of using |>
possible, but client
isn't the focus of many of the functions, nor is it transformed by many of the functions (the obvious exception is Forcex.Client
).
@sebbean First of all, thank you! |
Enables commands such as:
Looking to also implement a helper function for creating SObjects using Forcex.Client. Any thoughts or input?