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
This issue is requesting an enhancement to Perseus. Details of the scope will be available in issue labels.
The user described the problem related to this request as follows:
State amalgamation with different types
The user described the issue as follows:
State amalgamation currently uses the same state type for build type state, request time state, and amalgamated state. This makes using it a bit awkward since likely have to use some kind of enum with variants for the different kinds of states in it. It would be more convenient if you could just specify separate types for BuildTimeState, RequestTimeState and an fn amalgamate(BuildTimeState, RequestTimeState) -> AmalgamatedState function.
The author is willing to attempt an implementation: false
Tribble internal data
dHJpYmJsZS1yZXBvcnRlZCxDLWVuaGFuY2VtZW50
The text was updated successfully, but these errors were encountered:
This shouldn't be impossible, because Perseus only cares about state types at the very last second when it parses them to your custom functions, and, given enums aren't supported by the reactive state macro yet, I think this is perfectly reasonable. I'll get on this soon, but I'd be happy to accept a PR in the meantime!
This issue is requesting an enhancement to Perseus. Details of the scope will be available in issue labels.
The user described the problem related to this request as follows:
The user described the issue as follows:
Tribble internal data
dHJpYmJsZS1yZXBvcnRlZCxDLWVuaGFuY2VtZW50
The text was updated successfully, but these errors were encountered: