As mentioned in issue #172, the /api/transaction endpoint presents a security risk and doesn't align with Soul's philosophy of user-friendly, human-readable APIs accessible to non-SQL users.
Initially, this endpoint served as a tribute to the ws4sqlite library that inspired Soul's development. While I envisioned it as potentially useful, particularly with the introduction of authentication, it's become clear that the transaction endpoint is no longer a viable option. Therefore, I've decided to remove it.
As mentioned in issue #172, the
/api/transactionendpoint presents a security risk and doesn't align with Soul's philosophy of user-friendly, human-readable APIs accessible to non-SQL users.Initially, this endpoint served as a tribute to the ws4sqlite library that inspired Soul's development. While I envisioned it as potentially useful, particularly with the introduction of authentication, it's become clear that the transaction endpoint is no longer a viable option. Therefore, I've decided to remove it.