Setting a new alias makes exactly 2 requests #44

Open
opened 2025-03-27 10:00:58 +01:00 by kamikazechaser · 2 comments
  1. The first request sets the requested alias
  2. The seconds requests sets a random alias based on the input. This is the one displayed to the user.

Only one request should be sent. The alias service guarantees to return a name whether available or a random one in the first successful request.

1. The first request sets the requested alias 2. The seconds requests sets a random alias based on the input. This is the one displayed to the user. Only one request should be sent. The alias service guarantees to return a name whether available or a random one in the first successful request.
kamikazechaser added the
Kind/Bug
Priority
High
labels 2025-03-27 10:00:58 +01:00
Author
Owner

When updating an account with an existing alias. The same should be followed. Because we don't revoke previous aliases.

When updating an account with an existing alias. The same should be followed. Because we don't revoke previous aliases.
kamikazechaser added
Priority
Critical
and removed
Priority
High
labels 2025-03-28 06:10:53 +01:00
Member

This has been resolved on tag v1.0.0-rc.15.

Testing on staging before requesting deployment on production

This has been resolved on tag v1.0.0-rc.15. Testing on staging before requesting deployment on production
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: grassrootseconomics/sarafu-vise#44
No description provided.