You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I plan to rewrite serverside API in some parts, make it more Rust idiomatic. Mostly the baseobject API will change, I really want to get rid of Rc<RefCell<...>
And rework is also needed because clientside API is in progress and it already looks different from current serverside one
internal logging of altv crate should not set logger implementation and log level
reduce amount of panics due to unwrap() where base object may be null (see the case with player_leave_vehicle event when vehicle is destroyed), print warning or error instead
allow base object related calls from core when destruction or creation is pending? (see the case with player_leave_vehicle event when vehicle is destroyed) 4c44399
(?) hide scary BaseObjectContainer<..., ...> type from users by wrapping it into tuple structs with Deref impl (for example Vehicle is BaseObjectContainer<IVehicle, WorldEntity> currently)
remove re-exports of anyhow, serde, etc. from altv crate
The text was updated successfully, but these errors were encountered:
I plan to rewrite serverside API in some parts, make it more Rust idiomatic. Mostly the baseobject API will change, I really want to get rid of
Rc<RefCell<...>
And rework is also needed because clientside API is in progress and it already looks different from current serverside one
altv-rust/logger/src/lib.rs
Lines 38 to 39 in 757bc9e
BaseObjectContainer<..., ...>
type from users by wrapping it into tuple structs with Deref impl (for example Vehicle isBaseObjectContainer<IVehicle, WorldEntity>
currently)The text was updated successfully, but these errors were encountered: