[FIX] sign_oca: correct syntax and handle js logic#102
Conversation
|
Hi @etobella, |
3030a1a to
46ae26b
Compare
pedrobaeza
left a comment
There was a problem hiding this comment.
Please don't mix things in the same PR. I'm OK with the README change. If you publish it isolatedly, we can merge. But the other one is not clear how do you get to a situation where the element is not defined, and even if valid, you shouldn't log by console the warning. Just don't act.
just open my #99 and add a signature field when you fill it the error message will pop up, it is an error in UI not in the log. and in my PR there is no JS there! |
|
As said, please split both changes in 2 PRs for immediate merge of the README one, and the other shouldn't log to console. |
All right I will split them |
46ae26b to
51d90c0
Compare
#104 the readme one |
|
Enric, also the console.warn part? |
|
Sorry, I didn't read your comment about the log 🤔 Well, it is clear that would be better to ignore it if not found, however, I don't see the problem in leaving the warn. As both options work for me, I think that we should follow your suggestion and remove the warn. Can you do that @kobros-tech ? |
|
thank you both, sometimes I lose focus and I admit I just understood now what pedro said about consol log warn. I will work on it right now, some few please... |
51d90c0 to
365bfc4
Compare
|
Hey, thanks for contributing! Proceeding to merge this for you. |
|
the new module survey_sign_oca is ready for your review and comments, thanks! |
|
Congratulations, your PR was merged at ee49e9d. Thanks a lot for contributing to OCA. ❤️ |
Role correct syntax is between {{ }} not ${}, this will cause error. parent.items[nextItem.id] if is not defined the function dispatchEvent will throw error in the UI, so it is better to handle that error.