kellpossible / doublecount Goto Github PK

In a large system, using nanoid for account id's might cause a serious bug (people being able to edit accounts that aren't theirs). It would be good for people to provide their own id's, or at least think more about this issue.

Make it possible for people to use whatever ID system they want. The current default nanoid doesn't work with wasm-bindgen.

Consider using https://crates.io/crates/enum_dispatch instead of dynamic dispatch, or if I decide to value the ability to have users of this crate be able to implement their own Actions for the system, then figure out a way to remove the ActionType enum and replace it with something else, perhaps an integer order priority method for the Action trait.

See https://www.reddit.com/r/rust/comments/fr50vl/r2_a_router_in_rust/flucwb1?utm_source=share&utm_medium=web2x for what inspired me to create this issue

When re-loading data that has been serialised out of doublecount (e.g., to sqlite or serde once that's working), it'd be nice to be able to get the same ID for Account objects. Would this be Ok, or is there some good reason not to do it?