Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iOS-8994 feed back evolution #303

Merged
merged 13 commits into from
Sep 22, 2023
Merged

Conversation

WanaldinoTelefonica
Copy link
Contributor

@WanaldinoTelefonica WanaldinoTelefonica commented Sep 12, 2023

🎟️ Jira ticket

IOS-8994

πŸ₯… What's the goal?

  • Reduce side margins from 24px to 16px
  • Decrease icon size from 64 to 48
  • Custom success animation for Vivo_New
  • Add the new way to show the info animated

🚧 How do we do it?

  • Change properties
  • Replace json for new animation
  • Rewrite how the info is shown in view

πŸ§ͺ How can I verify this?

Grabacion.de.pantalla.2023-09-12.a.las.10.51.10.mov

πŸ‘ AppCenter build

image

@WanaldinoTelefonica WanaldinoTelefonica requested review from a team September 12, 2023 08:57
@WanaldinoTelefonica WanaldinoTelefonica self-assigned this Sep 12, 2023
@WanaldinoTelefonica WanaldinoTelefonica requested review from aweell, DavidMarinCalleja and alejandroruizponce and removed request for a team September 12, 2023 08:57
Copy link

@aweell aweell left a comment

Choose a reason for hiding this comment

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

Screenshot 2023-09-12 at 11 52 34

It seems that the asset in the error and success feedbacks is 48x48 but the info and feedback styles are keeping the 64 size?

Also the content of the latter is not animated?

@WanaldinoTelefonica
Copy link
Contributor Author

WanaldinoTelefonica commented Sep 12, 2023

Screenshot 2023-09-12 at 11 52 34

It seems that the asset in the error and success feedbacks is 48x48 but the info and feedback styles are keeping the 64 size?

Also the content of the latter is not animated?

Yes, thats right! Non animated images didn't resize into 48px correctly. Thanks!
New version generated with the fix πŸ˜„

What do you mean that latter content is not animated? If you refer to info style, specs only define that succes and error should.

@aweell
Copy link

aweell commented Sep 12, 2023

What do you mean that latter content is not animated? If you refer to info style, specs only define that succes and error should.

Sorry, not explicit enough with "latter" I was talking about the feedback style variant. The current web implementation was showing the animation but is because is being used as a base component for the other variants and the animation is configurable via prop. Forget about this :)

Comment on lines +354 to +362
if title.isEmpty == false {
views.append(titleLabel)
}
if let subtitle, subtitle.isEmpty == false {
views.append(subtitleLabel)
}
if let errorReference, errorReference.isEmpty == false {
views.append(errorReferenceLabel)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

This can be simplified by using the ! operator

Suggested change
if title.isEmpty == false {
views.append(titleLabel)
}
if let subtitle, subtitle.isEmpty == false {
views.append(subtitleLabel)
}
if let errorReference, errorReference.isEmpty == false {
views.append(errorReferenceLabel)
}
if !title.isEmpty {
views.append(titleLabel)
}
if let subtitle, !subtitle.isEmpty {
views.append(subtitleLabel)
}
if let errorReference, !errorReference.isEmpty {
views.append(errorReferenceLabel)
}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not a big fan of inverting booleans as I consider it is less readable.

Copy link
Contributor

Choose a reason for hiding this comment

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

In this case, Is this going to change the ViviΓ±o icon to Tick icon?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, only for success feedback screen

Copy link

@aweell aweell left a comment

Choose a reason for hiding this comment

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

There's an issue with the current lottie asset for the vivo success, causing an incorrect visualization. We're waiting for a new json file. I'll provide it here when we have it.

https://jira.tid.es/browse/OBVIVO-1792

Copy link
Contributor

@DavidMarinCalleja DavidMarinCalleja left a comment

Choose a reason for hiding this comment

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

@WanaldinoTelefonica WanaldinoTelefonica requested review from idenjoe and removed request for alejandroruizponce September 21, 2023 08:34
@aweell
Copy link

aweell commented Sep 21, 2023

There's an issue with the current lottie asset for the vivo success, causing an incorrect visualization. We're waiting for a new json file. I'll provide it here when we have it.

https://jira.tid.es/browse/OBVIVO-1792

New asset provided:

https://jira.tid.es/secure/attachment/2166789/f_feedback%20icon%20v3.json

@WanaldinoTelefonica
Copy link
Contributor Author

Hi @aweell! A new version has been upload with the new json file. Thanks πŸ˜„

Copy link

@aweell aweell left a comment

Choose a reason for hiding this comment

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

Nice job!

@WanaldinoTelefonica WanaldinoTelefonica merged commit 9bfe335 into main Sep 22, 2023
3 checks passed
@WanaldinoTelefonica WanaldinoTelefonica deleted the IOS-8994-FeedBack-evolution branch September 22, 2023 09:18
@tuentisre
Copy link
Collaborator

πŸŽ‰ This PR is included in version 26.1.0 πŸŽ‰

The release is available on GitHub release

Your semantic-release bot πŸ“¦πŸš€

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