profile-edit-traverse #199
Merged
lash
merged 26 commits from 2024-12-05 16:37:37 +01:00
profile-edit-traverse into master
Labels
Clear labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
cleanup
devops
documentation
easypeasy
exchange
i18n
legacy
meta
migration
optimization
privilege
refactor
smell
support
tooling
ux
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Activity
Doing
An item actively being worked on currently
Activity
Hold
Not being actively worked on
Activity
Proposal
A proposal for a new feature or enhancement
Activity
QA
Ready for QA testing
Activity
Validate
Dev team validating changes
Runner
AT
Runner
CLI
Runner
HTTP
Runner
SSH
A task that can be completed with little effort
relating to swapping of assets and offramps
Languages and translations
Legacy features from the old ussd system to be ported
container for other issues
features that have to do with special, privileged axx
Code smell
transparency and help with exception states
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: urdt/ussd#199
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes:
#80
#186
@@ -680,0 +731,4 @@func (h *Handlers) SetBack(ctx context.Context, sym string, input []byte) (resource.Result, error) {var res resource.Result//TODO://Add check if the navigation is lateral nav instead of checking the input.can we do this right now?
Based on tests i have done so far,it seems the INCMP _ 0 does not make the st.Lateral() evaluate to true,this will need some investigation or clarification if it is the expected behaviour.If this is the case, then we will probably need something similar to this to be able to do away with the input check for back.
@@ -1879,0 +1966,4 @@"flag_location_set","flag_offerings_set",}for index, profileItem := range h.profile.ProfileItems {isn't it easier and less code to iterate a map?
handled by commit:
321f038c7c@@ -187,6 +187,26 @@},{"input": "foo","expectedContent": "Enter family name:\n0:Back"are we still testing the case when profile information already has been set?
how about the test case where item 1 and 3 has been set, and we start at 2?
Yes ,there're test cases for when profile information is already set,i've added more test data files to handle the different test scenarios when editing the profile and for clarity:
22f96363ba@@ -1879,0 +1966,4 @@"flag_location_set","flag_offerings_set",}profileDataKeys := map[int]common.DataTyp{IIRC this was the switch-case statement previously?. This can still be an array, and profileDataKeys[index] can address the index in the array?