Fix sorting of message enum variants

This commit is contained in:
Keavon Chambers
2022-01-16 13:59:55 -08:00
parent 1a4ab0733b
commit 841f34e797
25 changed files with 254 additions and 111 deletions
+2 -1
View File
@@ -58,6 +58,8 @@ impl Dispatcher {
// Process the action by forwarding it to the relevant message handler, or saving the FrontendMessage to be sent to the frontend
#[remain::sorted]
match message {
#[remain::unsorted]
NoOp => {}
Frontend(message) => {
// `FrontendMessage`s are saved and will be sent to the frontend after the message queue is done being processed
self.responses.push(message);
@@ -74,7 +76,6 @@ impl Dispatcher {
InputPreprocessor(message) => {
self.message_handlers.input_preprocessor_message_handler.process_action(message, (), &mut self.message_queue);
}
NoOp => {}
Portfolio(message) => {
self.message_handlers
.portfolio_message_handler
+2 -1
View File
@@ -20,6 +20,8 @@ where
#[impl_message]
#[derive(Clone, Debug, PartialEq, Serialize, Deserialize)]
pub enum Message {
#[remain::unsorted]
NoOp,
#[child]
Frontend(FrontendMessage),
#[child]
@@ -28,7 +30,6 @@ pub enum Message {
InputMapper(InputMapperMessage),
#[child]
InputPreprocessor(InputPreprocessorMessage),
NoOp,
#[child]
Portfolio(PortfolioMessage),
#[child]