summaryrefslogtreecommitdiff
path: root/rust/src/repository/plugin.rs
AgeCommit message (Collapse)Author
2026-05-05Expose 'is_paid' Extension field in API0cyn
2026-05-04Re-add license text field to API0cyn
2026-04-22Expose all version-specific info for extensions in API0cyn
2026-04-14Plugin Manifest V2 Support0cyn
2025-11-03Revert "Refactor Plugin Load/Management to support upcoming changes"0cyn
This reverts commit 72fcf44f3731ade3cf1310da55f633f1cb9069ce.
2025-10-29Refactor Plugin Load/Management to support upcoming changes0cyn
2025-05-12[Rust] Reduce usage of `IntoCStr` in function signaturesMason Reed
This is being done to reduce complexity in function signatures, specifically many of the strings we are passing ultimately should be new types themselves instead of "just strings", things such as type ids. Another place which was confusing was dealing with filesystem related APIs, this commit turns most of those params into a stricter `Path` type. This is bringing the rust api more inline with both python and C++, where the wrapper eagerly converts the string into the languages standard string type. Special consideration must be made for symbols or other possible non utf-8 objects. This commit will be followed up with one that adds the `IntoCStr` bound on API's we want to keep as invalid utf-8 so we can for example, get section by name on a section with invalid utf-8.
2025-05-12[Rust] Return `String` instead of `BnString` for cases where lossy ↵Mason Reed
conversion can be tolerated Still need to go and audit all usage, but realistically the most important places to give the user control are with symbols, where the data can come from non utf8 sources This is still incomplete, I just looked for usage of -> BnString so any other variant was omitted.
2025-02-07Fix incorrect casts in Rust RepositoryPluginMason Reed
Was causing linux arm builds to fail
2025-02-06Implement Rust RepositoryRubens Brandao