Hey guys, so sorry to keep you waiting. We've been keeping the pool of active Treeline users small to limit the number of projects that will require manual migrations when we ship the next release. It's a big one: it fixes some major bugs, as well as lifting limitations around loops, dynamically-typed data, and convergence. We are also in the middle of some low-level improvements that will help make Waterline more robust and user-friendly w/ analog usage (i.e. in your hand-written Sails app or from a vanilla Node process).
The entire core team from Sails is working at Treeline full time, and we're committed to finishing this release asap-- but at the same time, we're obsessed with making sure that the tool is at least as flexible, stable, consistent, and usable as what we're all using today for backend dev (e.g. Sublime). And we're also taking great care to make sure the work we're doing strengthens the Sails and Waterline ecosystems, regardless of whether you're using Treeline or not.
So stay tuned- but in the mean time, if you're interested in what we're doing or want to contribute, please try building some analog machines and let us know any limitations or questions you have in the Google group. The machine spec is a core part of what we're doing with Treeline, and it will also play a big role in the development of Sails and Waterline going forward. Your feedback at this stage is really important to us.
@Geocloud I wrote the mp for authorize.net and yelp. In controller
var AuthorizeNet = require('machinepack-authorizenet');
AuthorizeNet.createTransactionRequest({
transactionKey: 'secret',
apiLoginId: 'secret',
amount: paypalOptions.total,
currency: 'usa',
cardnumber: paypalOptions.eccnum,
cardexpmonth: paypalOptions.cbexpdatem,
cardexpyear: paypalOptions.cbexpdatey,
cvv2: paypalOptions.ecvc,
billingFirstName: 'john',
billingLastName: 'Thomas',
billingAddress1: "500 5th Ave",
billingCity: "New York",
billingState: 'NY',
billingPostalCode: '10011',
billingCountry: 'USA'
}).exec({
// An unexpected error occurred.
error: function (err) {
return res.json(err);
},
// OK.
success: function (newCharge) {
console.log('Stripe result ', newCharge.id, newCharge.source.id)
var upstr = ' execute procedure "SP Member EnrollPart3"(%s,%s,%s,%s,%s ,%s,%s,%s,%s,%s ,%s,%s,%s,%s,%s, %s)';
var upstr2 = util.format(upstr,
bq(paypalOptions.memid),
bq(paypalOptions.payoption),
bq(paypalOptions.promocode),
bq(paypalOptions.password),
bq(paypalOptions.subtotal),
bq(paypalOptions.processingfee),
bq(paypalOptions.total),
bq(paypalOptions.cbcardtype),
bq(paypalOptions.eccnum),
bq(paypalOptions.ecvc),
bq(paypalOptions.cbexpdatem),
bq(paypalOptions.cbexpdatey),
bq(paypalOptions.autopayment),
bq(newCharge.id),
bq(newCharge.source.id),
bq(newCharge.status));HTH
machinepack-process, machinepack-fs, and machinepack-mysql are out. (Major caveat is that you can't use them in Treeline yet, but we're working on that).
machinepack-http is broken in recent release. It shows in docs (http://node-machine.org/machinepack-http/send-http-request) that there are formData and params but they are not specified in input for machinepack anymore. https://runkit.com/582c52bc7f8b590013d4197b/5837191997657a0014e10e38
require to avoid malicious code injection, but to still allow machine definitions to be normal JavaScript. Unfortunately, this also prevents the use of constants, which are handy. Since the machines in question were using constants, they were skipped during import.
To fix this, we added special exception, allowing machines to require from the top-level constants folder in the machinepack.
Note that this restriction is only OUTSIDE of the
fn-- you can make anyrequirecall you like inside of thefn.