Update to Spin SDK 3.x

[itowlson]

It was previously on 0.4 which was causing downstream projects some ructions! If there's a better way to manage the new async send then please go ahead, I just didn't know how to handle it in that macro!

(And I haven't been able to test, I'm afraid, because no Twitter.)

[itowlson]

Oops. Converting to draft because there are some other conflicts too.

[itowlson]

No there aren't, I'm just an idiot. Ready to review after all!

[rajatjindal]

Hi @itowlson, were you able to test this? If so I am happy to just merge it.

[itowlson]

@rajatjindal I don't actually know how to test it. I tried a naive variation of the basic example but mine failed with an enigmatic parse error. If you have an example of using it then I can give it a go.

What I tried:

use handlebars::Handlebars;
use handlebars_sprig;

fn main() {
    // Get a handlebars instance
    let mut hbs = Handlebars::new();

    // THE IMPORTANT PART: Add the helpers
    handlebars_sprig::addhelpers(&mut hbs);

    // From this point, you can do whatever you want to do with the
    // handlebars instance. It will have all of the functions available
    // to the templates.
    let tpl = "{{ tweet fermyontech 1868691973097562174 }}";

    // Example of running a template render.
    let empty_context: Vec<String> = vec![];
    println!(
        "Template produced: {}",
        hbs.render_template(tpl, &empty_context).unwrap()
    )
}

Result:

thread 'main' panicked at src/main.rs:20:50:
called `Result::unwrap()` on an `Err` value: RenderError { desc: "Cannot access array/vector with string index.", template_name: None, line_no: Some(1), column_no: Some(1), cause: Some(ParseIntError { kind: InvalidDigit }), unimplemented: false }

(line 20 is the render_template call)