gRPC: lightningd: Fix empty description field in listpays & listsendpays #8803
+35
−5
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.
Not ready to merge.
Fixes #7973.
This PR fixes the description field being returned as empty in gRPC responses for listpays and listsendpays.
The field already existed, but was not being populated correctly in these gRPC paths.
After this change, the description is correctly propagated and returned for completed payments.
Examples:
No schema change is required: the description field already existed in both the database and RPC definitions.
The fix ensures the field is correctly populated and forwarded in gRPC responses.
Existing SQL tests pass without modification, since description is an additional optional field and does not affect existing column expectations.