profile-edit-traverse #199

Merged
lash merged 26 commits from profile-edit-traverse into master 2024-12-05 16:37:37 +01:00
Member

Fixes:
#80
#186

Fixes: #80 #186
carlos added 5 commits 2024-12-03 09:26:12 +01:00
carlos added 3 commits 2024-12-03 12:41:20 +01:00
carlos added 2 commits 2024-12-03 15:41:28 +01:00
carlos added 2 commits 2024-12-03 20:30:57 +01:00
carlos added 4 commits 2024-12-04 06:30:50 +01:00
carlos added 2 commits 2024-12-04 07:09:06 +01:00
carlos added 1 commit 2024-12-04 07:46:33 +01:00
carlos changed title from WIP: profile-edit-traverse to profile-edit-traverse 2024-12-04 11:06:24 +01:00
lash requested changes 2024-12-04 16:59:40 +01:00
Dismissed
@ -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.
Owner

can we do this right now?

can we do this right now?
Author
Member

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.

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 {
Owner

isn't it easier and less code to iterate a map?

isn't it easier and less code to iterate a map?
Author
Member

handled by commit: 321f038c7c

handled by commit: 321f038c7ce4492d05bd35572e68d669b7c05a9b
@ -187,6 +187,26 @@
},
{
"input": "foo",
"expectedContent": "Enter family name:\n0:Back"
Owner

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?

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?
Author
Member

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

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: 22f96363ba61352cc23868f5f0d26b75915e0971
carlos added 1 commit 2024-12-05 09:15:53 +01:00
carlos added 1 commit 2024-12-05 10:22:46 +01:00
carlos added 2 commits 2024-12-05 12:06:22 +01:00
carlos added 1 commit 2024-12-05 14:03:40 +01:00
lash requested changes 2024-12-05 16:02:44 +01:00
Dismissed
@ -1879,0 +1966,4 @@
"flag_location_set",
"flag_offerings_set",
}
profileDataKeys := map[int]common.DataTyp{
Owner

IIRC this was the switch-case statement previously?. This can still be an array, and profileDataKeys[index] can address the index in the array?

IIRC this was the switch-case statement previously?. This can still be an array, and profileDataKeys[index] can address the index in the array?
carlos added 1 commit 2024-12-05 16:26:12 +01:00
carlos added 1 commit 2024-12-05 16:34:50 +01:00
lash approved these changes 2024-12-05 16:37:29 +01:00
lash merged commit 43892f0d8c into master 2024-12-05 16:37:37 +01:00
Sign in to join this conversation.
No reviewers
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: urdt/ussd#199
No description provided.