Open aruokhai opened 9 months ago
@aruokhai thanks for looking at this. This is going to make much more sense after merging #190, which gets rid of all in-memory data for the tower. Hence, a big refactor will be needed, but it would make the change way smaller. I'd suggest you wait until that is landed and take another look at it.
@aruokhai we just landed #190
would take a look at it again and start working on a new fix
added the necessary changes
Objective Ensure locators are returned instead of uuid's under appointments section when user details are fetched through the cli using the getuser command.
Problem
locator
is an appropriate identifier for appointments in the Bolt13 specification draft, which is also being used in thegetappointments
cli command , but in thegetuser
cli command uuid is being used which can be confusing . The solution is ensuregetuser
cli command makes use oflocator
and notuuid
.Changes
get_user_info
function to make use of locator and not uuid when returning user appointments info.get_user
test to reflect the change from uuid to locator.Scope Of Change This is a non critical change, as it only affects the CLI.
closes #229