The following is the list to do for chatroom implementation.

• docker django-redis
• channels
• websocket
• chatroom frontend

We need to implement demo-index component

We need to complete the specific UI of the profile page.

For use in the user-entry component (input component where user can type username to get the user dropdown). It was missing in the design doc.

index page must be different before and after login.

Header and footer, which will be used in every single page, are required to be implemented.

We have to delete forms.py and add more exception control for signin, signout, signup

제가 어제 실습 시간에 올렸던 lint 파일이 아직 완성이 되지 않았는데 pylint 부분까지 추가해서 설정파일을 수정해주시면 감사하겠습니다.

We need to set frontend structure and add route

The following pages need to be implemented.

• signup page
• index page (before sign-in)

Transaction list on each Loan component is needed.

We find so many errors when we test the front.
We need to fix these kind of errors; console.error node_modules/*.

App.jsx should be fixed like this:

However, when I fixed it this way, there was a problem in LoginPage test.
I guess that is because of a change in routing.
Hence, I decided to push App.jsx file just as before.
The person in charge of the login test should modify the login test for the above version of App.jsx file.
Please fix this problem!

Use
PropTypes.objectOf(PropTypes.object()),

instead of
PropTypes.object

• container and styled presenter

We must add some sort of API and some sort of mechanism to send notifications to users via phone calls or SMS messages.

I uploaded the outlook of the document and every part that I took on. Please finish the rest of the parts allocated to you.

Please know that the component diagram should be updated with your parts! Please comment on this issue when you are done with your own part.

• Let sonarcloud receive coverage reports
• Set up coveralls
• Add bages (missing: coveralls, sonarcloud)
• (Optional) move to travis-ci.org.

pylint is preventing our build from succeeding.

• Look into https://pypi.org/project/pylint-django/

Other .css file may not be that important, but I think implementing this with .css is especially important.

part of #24 .

Branch [loans-create] is successfully merged into master. Please delete branch [backend-loans], which is for backup, after your own review.

What we are doing good

• Every code style, code smell, and coverage is checked by CI(travis.ci, SonarCloud).
• GitHub configuration (force not to push to master branch directly)

What we have to improve

• Test more exception cases
• Try to increase the coverage of the overall codes
• Refactoring is required

We should not have the package.json and yarn.lock file at the root of the repository. They seem to have been added in #37.

Please close this issue if this was done on purpose, otherwise we should merge the dependencies into frontend/package.json.

https://docs.google.com/presentation/d/156WHT6rIYn5o37NtJXTcZUh-bOAznCv-eBbKXFeP0DE/edit?usp=sharing

We need to implement review model

Create loan button must open create loan page.

It will be helpful to implement frontend subcomponents such as validator, TextField, Buttons, and so on.

We need api for getting user info and updating user profile

I am going to make the overall models and urls for this project.

Since our sonar-project.properties doesn't exclude the test files from the testing, our quality gate status is 'failed' at this point. We need to make modifications to the configuration file.

Create both the frontend & backend for loan creation.

We merged the PR that didn't pass the automated test at #10 in order to set the linter ASAP. Now we need to fix the code to meet the design plan and the coding convention that we decided.

part of #24

I am working on

• App.jsx
• Header.jsx
• LoginPage.jsx
• utils.js

I will implement demo index page and finish the signin, signup page UI. Can anyone please review the code afterwards?

There needs some modification in backend models to support new features implemented.

In account.profile:

• twillio_msg: the message to be uttered when the system gives a call to users who didn't payback.
• rating: the credit rating score calculated by sentimental analysis

/profile/:(user_id)
opens current user's profile page
/profile/:(id)
opens the profile page of a user whose id is (id)
/profile
redirects to /profile/:(user_id)

with styled

In our design documents, we specified that a user creates a new loan by sending a POST request to /loans/{id}. However, this should be sent to just /loans to match traditional REST semantics as well as allowing users to create new users without having to know the last allocated ID.

We have to show current user's name on frontend, and that function must be implemented on backend

Loan list component(Ongoing&Done) on each user is needed.

We must allow users to confirm loan status. Also, notify affected parties (see #93).

This component is a requirement for implementing #24. I have already started work in frontend-userentry, and part of the API is already completed (although we may need to implement more API endpoints before being able to fully implement this component).

The validator, which is a library to validate string type(email, phone #, postal code ...), is really useful. I already added it to our packages.

How To Use

import

import isEmail from 'validator/lib/isEmail';

or

import isEmail from 'validator/lib/isEmail';

usage

<script type="text/javascript" src="validator.min.js"></script>
<script type="text/javascript">
  validator.isEmail('[email protected]'); //=> true
</script> 

For more information, please check this documentation