Skip to content

[18.0][IMP] sign_oca: Add guided arrow flow to sign_oca#80

Closed
kobros-tech wants to merge 3 commits intoOCA:18.0from
kencove:18.0-imp-sign_oca-3
Closed

[18.0][IMP] sign_oca: Add guided arrow flow to sign_oca#80
kobros-tech wants to merge 3 commits intoOCA:18.0from
kencove:18.0-imp-sign_oca-3

Conversation

@kobros-tech
Copy link
Contributor

@kobros-tech kobros-tech commented Jan 30, 2025

add arrow / guided flow to sign_oca

#88

@OCA-git-bot
Copy link
Contributor

Hi @etobella,
some modules you are maintaining are being modified, check this out!

@pedrobaeza pedrobaeza added this to the 18.0 milestone Jan 30, 2025
@kobros-tech kobros-tech force-pushed the 18.0-imp-sign_oca-3 branch 2 times, most recently from 324f59f to ab74e88 Compare January 30, 2025 23:16
@kobros-tech
Copy link
Contributor Author

This is how the arrow should look like:
@dnplkn

Screenshot from 2025-01-31 02-12-36

@kobros-tech
Copy link
Contributor Author

kobros-tech commented Feb 2, 2025

Copy link
Member

@etobella etobella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You left a lot of console logs and comments to your name that don't have sense. Please remove them and add some comments on the functions explaining the goal of each one. I don't understand why you need to remove them from the core file if they are only used on a single place....

* @param { Environment } env
*/
export function startSignItemNavigator(parent, target, types, env) {
console.log("types", types);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't leave this

@victoralmau
Copy link
Member

Why are the changes of #78 also added here? I don't understand it.

@kobros-tech
Copy link
Contributor Author

hi all
thanks for contributing with me.

this module is under development, so if we can cooperate in the main important cause of it is more effective.

Once it is working as expected all normal procedures will be done.

Thanks all

@etobella etobella changed the title [18.0][IMP] sign_oca: Add guided arrow flow to sign_oca [DRAFT][18.0][IMP] sign_oca: Add guided arrow flow to sign_oca Feb 3, 2025
@kobros-tech kobros-tech force-pushed the 18.0-imp-sign_oca-3 branch 6 times, most recently from 0a044ca to f0dbb2e Compare February 9, 2025 02:54
@kobros-tech
Copy link
Contributor Author

@dnplkndll
We can see some design errors only if we shrink or maximize browser window, but the arrow functionality is correct in both browsers [Firefox, Chrome]

I enabled auto check of the checkbox, the default is when it is selected you can press on space button to check or un check it.
So my extra option is not very important except in fast document filling.

The module is ready for review for all its fields fillings.

Screencast.2025-02-09.06.22.08.mp4

@kobros-tech kobros-tech changed the title [DRAFT][18.0][IMP] sign_oca: Add guided arrow flow to sign_oca [18.0][IMP] sign_oca: Add guided arrow flow to sign_oca Feb 9, 2025
@kobros-tech
Copy link
Contributor Author

f2f25ed

The solution is to reprepare fields to follow and to make sure that the navigator div is created ONLY once.
I wish there is no any remaining bugs.
https://github.com/user-attachments/assets/f14d8a7e-d820-4835-bbf9-7e1b5021140f

@kobros-tech
Copy link
Contributor Author

there is a bug with the original module which is:

if someone fills all required fields and then clear one field the validate button still clickable, even after validation error if the partner fills the fields the validation button is still not clickable.

We have to check it after filling each field value.

@kobros-tech
Copy link
Contributor Author

@etobella
@victoralmau
can we review this PR and the many others that improves the module functions?

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants