Require finishing function to be called?

[lkdm]

Hello! I've created a builder that creates a SqliteAdapter newtype either in memory or with a connection to a database using a PathBuf.

Is there a way for me to require that the developer explicitly run_migrations as part of the builder?

/// SqliteAdapter
///
/// An adapter for the application that implements SQLite.
pub struct SqliteAdapter(Connection);

#[bon]
impl SqliteAdapter {
    /// Creates a new SqliteAdapter
    #[builder]
    fn path(path: PathBuf) -> Result<Self, AdapterError> {
        let cnx = Connection::open(path)?;
        Ok(SqliteAdapter(cnx))
    }
    /// Creates an in-memory SqliteAdapter for the purpose of testing
    #[builder]
    fn in_memory() -> Self {
        match Connection::open_in_memory() {
            Ok(cnx) => SqliteAdapter(cnx),
            _ => panic!("Could not open Sqlite connection in memory."),
        }
    }
    /// Run migrations – should be called before SqliteAdapter is used
    fn run_migrations(&mut self) -> Result<(), rustqlite::Error>;
 }
 
 // Ideal syntax would look like:
 // SqliteAdapter::in_memory().run_migrations().call();
 // And ideally:
 // SqliteAdapter::in_memory().call() // Should panic or warn developer.

I looked into finish_fn, but that just renames call.

Thanks again for this great crate– I use it all the time :)

[lkdm]

Forgive me because I'm a Rust noob– but having thought about it, the body of the method is the finishing function:

    #[builder(finish_fn = init)]
    fn in_memory() -> Self {
        match Connection::open_in_memory() {
            Ok(cnx) => {
                let mut adapter = SqliteAdapter(cnx);
                adapter.run_migrations().expect("Migrations should run as expected");
                adapter
            }
            _ => panic!("Could not open Sqlite connection in memory."),
        }
    }

[Veetaha]

That's okay, it takes some time for people to get used to thinking with function-based builders 🐱. Feel free to post questions

[lkdm]

Thanks, I appreciate your reply. I always leave my answers up because hopefully it’ll help someone else.

Cheers 😁