The only problem is I'm pushing the limits of browser memory/CPU on some customer accounts so I've made some performance optimizations like only rendering the hidden fields once the submit button is pushed. It sounds crazy but it was actually really simple to do and is only a temporary transitional thing. I plan on publishing it soon OSS as RailsForm.vue. Including nested arrays of objects, with any degree of nesting. I built a Vue component that automatically generates Rails friendly forms from any object. If prompted, complete steps for multifactor authentication (if it is enabled on your account). On one page there could be hundreds of records because some customers like to create a thousand objects for one marketing 'campaign' and have customers routed (via IVR or geo or other flags from the source website/ad embedded js) to a thousand different sales agents depending on fine-tuned criteria (like if they press 1 to say they are over 50), and from there it could trigger a hundred different conversion triggers (for ex: to do CPA payouts to the traffic sources) and webhooks to various analytics services.Īnyway I'm slowly redesigning each part of the giant forms one-by-one and instead of AJAXing some parts separately I'm injecting the data into hidden fields which get submitted via traditional HTTP form-data along with the old forms. Check your Preferences by doing either of the following: In your web browser toolbar, click the inactive (grey or black) LastPass icon. I'm building very complex B2B software (link to company is in profile) doing phone call tracking and its a large legacy Rails app with standard `form_for` type forms.
0 Comments
Leave a Reply. |