Conversation
raffael0
force-pushed
the
field_responses
branch
2 times, most recently
from
c3b4d20 to
038e0f0
Compare
raffael0
force-pushed
the
field_responses
branch
from
038e0f0 to
e764f1e
Compare
miDeb
approved these changes
Feb 28, 2026
raffael0
added a commit
that referenced
this pull request
Feb 28, 2026
Updated the version number for the #7 Pull Request
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes the issue that we previously did not define what the server should respond, when it does not have corresponding field registered. To fix this I added a status field to the response messages
Additionally i've added a ci script, so that you can run and fix formatting/linting issues locally. See: ci-rust.sh
Here is the document diff:
LiquidCAN-diffmain.pdf