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

Add Dashboard and Authentication (Login, Signup) components #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

CajetanRodrigues
Copy link

@CajetanRodrigues CajetanRodrigues commented Aug 20, 2019

Dashboard and Login Component Improvements

  • Integrated the APIs for the Sign-Up Component, Login Component and the Dashboard Component
  • Improved the behavior of the side navbar based on appropriate conditions and user login status.
  • Proof-checked the responsiveness for mobile and desktop screens.
  • Standardized fonts across the app.
  • Added AOS animation for animate on scroll functionality.

UI Demonstration

edit

UI ScreenShots

Login Component

login

Forgot Password Component

forgot-password

Sign Up Component

signup-final

Dashboard Component (Desktop Version)

dashboard-final

Dashboard Component (Mobile Version)

dashboard-final-mobile-1

@CajetanRodrigues CajetanRodrigues force-pushed the fix-login-bug branch 12 times, most recently from fde51de to 0b89931 Compare August 21, 2019 10:49
@CajetanRodrigues CajetanRodrigues changed the title Add UI improvments Add UI improvments for Dashboard and Authentication components Aug 21, 2019
@CajetanRodrigues CajetanRodrigues force-pushed the fix-login-bug branch 2 times, most recently from 783157d to c2434ab Compare August 21, 2019 17:55
@ankit01ojha
Copy link
Collaborator

@CajetanRodrigues, sometimes I am getting this on the landing page
Uie2

@CajetanRodrigues CajetanRodrigues force-pushed the fix-login-bug branch 4 times, most recently from 50a8eec to 56719b1 Compare August 22, 2019 13:51
@CajetanRodrigues
Copy link
Author

@CajetanRodrigues, sometimes I am getting this on the landing page
Uie2

I have resolved it

@CajetanRodrigues CajetanRodrigues force-pushed the fix-login-bug branch 2 times, most recently from 9b17d22 to d5f7322 Compare August 22, 2019 14:12
@CajetanRodrigues CajetanRodrigues changed the title Add UI improvments for Dashboard and Authentication components Add Dashboard and Authentication (Login, Signup) components Aug 22, 2019
src/app/app.component.html Outdated Show resolved Hide resolved
src/app/services/authentication.service.ts Show resolved Hide resolved
const httpOptions = {
headers: new HttpHeaders({ 'Content-Type': 'application/json',
'Fineract-Platform-TenantId': 'mobile',
Authorization: 'Basic bWlmb3M6cGFzc3dvcmQ=' })
Authorization: 'Basic bWlmb3M6cGFzc3dvcmQ=',
Copy link
Collaborator

Choose a reason for hiding this comment

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

@CajetanRodrigues hardcoded.

Copy link
Author

Choose a reason for hiding this comment

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

Ok I will resolve that

Copy link
Author

Choose a reason for hiding this comment

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

@CajetanRodrigues Login using a recently registered user is not working.

I have resolved that. You can now sign up and login the same credentials you put in the form. Although the authentication flow is temporary, we could fix it in the near future. For now this PR needs to get merged to have the base fixed once and for all. So that I as well as upcoming contributors can create new components on top of the base.

Copy link
Collaborator

@ankit01ojha ankit01ojha left a comment

Choose a reason for hiding this comment

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

@CajetanRodrigues why username: mifos and password: password is working here, it should not work because there is no self service user as mifos. openMF/web-self-service-app#27

Copy link
Collaborator

@ankit01ojha ankit01ojha left a comment

Choose a reason for hiding this comment

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

@CajetanRodrigues Login using a recently registered user is not working.

@CajetanRodrigues
Copy link
Author

CajetanRodrigues commented Aug 25, 2019

@CajetanRodrigues login still has issues. When I login with right credentials it is first showing an invalid credential message and then it shows login successfully. And if a user is not a self-service user it is showing invalid credentials message rather than not a self-service user. Name of the client fetched is wrong. And could you change the UI of the landing page similar to the old one?

Re:
I have resolved all the login errors and stated proper login messages now. Also, the UI of the landing page is the same as the old app. Since this is Angular Material with Angular 7, the UI would look a bit different, but the rest of the things have been resolved and all the above changes have been taken into consideration.

@gauravsaini03 Can you take a final look?

@@ -1,9 +1,9 @@
<form #loginForm="ngForm" >
<img src="https://www.google-melange.com/archive/gci/2014/orgs/mifos/logo-200.png" alt="No Image found">
<mat-form-field>
<mat-form-field class="font-style ">
Copy link
Member

Choose a reason for hiding this comment

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

Please remove space in the class

Copy link
Author

Choose a reason for hiding this comment

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

okay sure

Copy link
Author

Choose a reason for hiding this comment

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

Hi Gaurav, as you have suggested. I have indented all the code.

@ankit01ojha
Copy link
Collaborator

ankit01ojha commented Aug 25, 2019

Also, the UI of the landing page is the same as the old app. Since this is Angular Material with Angular 7, the UI would look a bit different.

So, you mean that the size of the font, position of font, spacing, and colors in button are different because you are using Angular Material with Angular 7 and not because of CSS? Modify the CSS to make it similar to the UI of the landing page of web self-service app because UI landing page of web self-service app is quite good.

@CajetanRodrigues
Copy link
Author

CajetanRodrigues commented Aug 25, 2019

Also, the UI of the landing page is the same as the old app. Since this is Angular Material with Angular 7, the UI would look a bit different.

So, you mean that the size of the font, position of font, spacing, and colors in button are different because you are using Angular Material with Angular 7 and not because of CSS? Modify the CSS to make it similar to the UI of the landing page of web self-service app because UI landing page of web self-service app is quite good.

No, I didn't mean that. I will do the needful. Thanks for reviewing

Copy link
Collaborator

@ankit01ojha ankit01ojha left a comment

Choose a reason for hiding this comment

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

@CajetanRodrigues you need to fetch the details of the client who has logged in and display their details in dashboard. I don't see you fetching the login clients details.

And do the change the UI of the login page, it's still the same.

@CajetanRodrigues
Copy link
Author

CajetanRodrigues commented Aug 26, 2019

@CajetanRodrigues you need to fetch the details of the client who has logged in and display their details in dashboard. I don't see you fetching the login clients details.

And do the change the UI of the login page, it's still the same.

  • Made the look of login page as similar as possible to the Online Banking App 2.0
  • Fetched display name & display picture of client from API and integrated with the app

Copy link
Collaborator

@ankit01ojha ankit01ojha left a comment

Choose a reason for hiding this comment

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

@CajetanRodrigues Why there are so many unwanted undefined requests are being sent in the background? When being logged in for the first time the loader keeps on loading( maybe because of these unwanted error requests). Fix them. And why are you saving the image of the client in the local storage? Remove that too.

@CajetanRodrigues CajetanRodrigues force-pushed the fix-login-bug branch 5 times, most recently from 4e2733e to 477dc22 Compare August 27, 2019 14:25
@CajetanRodrigues
Copy link
Author

@CajetanRodrigues Why there are so many unwanted undefined requests are being sent in the background? When being logged in for the first time the loader keeps on loading( maybe because of these unwanted error requests). Fix them. And why are you saving the image of the client in the local storage? Remove that too.

  • Removed unwanted undefined get requests
  • Removed image from local storage
  • Resolved the problem, where spinner loads on the first login and data was not able to load.

Copy link
Collaborator

@ankit01ojha ankit01ojha left a comment

Choose a reason for hiding this comment

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

@CajetanRodrigues remove inline CSS.

Copy link
Collaborator

@ankit01ojha ankit01ojha left a comment

Choose a reason for hiding this comment

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

@CajetanRodrigues Client's name is missing and charts are not correct for the client, tally it with the old app and fix it.

@CajetanRodrigues
Copy link
Author

@CajetanRodrigues remove inline CSS.

  • Proof checked entire html code for inline css and removed wherever present.
  • Added Stylings in external scss file.

@CajetanRodrigues
Copy link
Author

@CajetanRodrigues Client's name is missing and charts are not correct for the client, tally it with the old app and fix it.

  • Fixed the issue that the client name was not visible after reloading of page, but available after immediate login.
  • Tallied the data with the old app.

@CajetanRodrigues CajetanRodrigues force-pushed the fix-login-bug branch 2 times, most recently from 36ac98d to c2fb688 Compare September 1, 2019 10:25
Copy link
Collaborator

@ankit01ojha ankit01ojha left a comment

Choose a reason for hiding this comment

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

@CajetanRodrigues I cannot see clients APIs being called. You need to fetch clients details because if it shows no content then only you can differentiate between a self service user and a non self service user.

headers: new HttpHeaders({
'Content-Type': 'application/json',
'Fineract-Platform-TenantId': 'mobile',
Authorization: 'Basic bWlmb3M6cGFzc3dvcmQ='
Copy link
Collaborator

Choose a reason for hiding this comment

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

@CajetanRodrigues hardcoded.

Copy link
Author

Choose a reason for hiding this comment

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

  • I have done the changes. It now fetches the token dynamically.

@CajetanRodrigues
Copy link
Author

CajetanRodrigues commented Sep 2, 2019

@CajetanRodrigues I cannot see clients APIs being called. You need to fetch clients details because if it shows no content then only you can differentiate between a self service user and a non self service user.

  • You can find the client.service.ts file where I have defined methods for fetching client details
  • I have called the same methods in app.component.ts , dashboard.component.ts & individual chart components

Copy link
Collaborator

@ankit01ojha ankit01ojha left a comment

Choose a reason for hiding this comment

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

@CajetanRodrigues you are not checking whether clients are associated with that user or not, and without doing that how are you classifying whether a user is a self-service user or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants