Write tests for #66 feature

If we get some error on API (4xx or 5xx), we should be showing something on the screen, currently the screen simply goes blank and we see the API error in console

We should be sending company in signup form than company_name

The website input field on signup form should be optional. The label says it is optional but it is not optional 😅

We need to fix it.

Sign up flow: Framer Link

• Update npm packages
• Update to Ember 3.25
• Set port as 80

Description

Pre commit will be used for avoiding the linting issues.

If we click on tasks in navbar, it takes a while to load. Better to show a spinner

Create the following feature for my.realdevsquad.com index page

If the user is idle, we will show them on https://status.realdevsquad.com/idle-members

Design here

Similar to this PR

Render human readable date (like 8 days later (22 May)), instead of the milliseconds since epoch value

Instagram id field is missing on the signup form

Just check @tracked fields inside app/controllers/signup.js and you'll understand what is to be done 😉

This component exists on index page

Design here

Once #67 is merged, you can just run the test suite: npx ember test --server --filter="Integration | Component | self-clear-cache" and make it pass.

• Ability to update profile
• All fields available in signup are visible (some disabled)

• See users tasks and update progress on them
• Track status of dependent tasks

Requirements:

The tasks on my site should have certain restrictions:

• At most, one task can be in active state - Shows in first row
• Blocked tasks show in second row
• Completed tasks are hidden until the tab clicked from row three
• Cannot add/remove tasks
• Completion percentage can be changed
• Can mark task as blocked

Location:

Duplicated Code
Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

We're using font-awesome library now, CDN is not needed anymore
It was added in PR #53

Optional fields if left empty are being sent as empty string which is not allowed by the backend.
We should not be sending empty strings in the first place.

On the signup page after filling details and submitting the form, we are getting some console errors. For some reference please refer to screenshots.

Need to update the packages

When the user clicks submit, if the success response is ok, we should disable the submit button and show some kind of loader so that the user knows something is going on and the user is not supposed to hit submit button again

Configure ESLint

The user should be able to understand that something is happening after clicking the submit button and hence we should some kind of loader or spinner to indicate that API calls are indeed taking place and disable the submit button.

Tests for #65 feature

• First Name
• Last Name
• Username (Guide them more)

Show customized notifications to the user

Figma Link

• Stage-1: Ticket for non-debounce slider
• Stage-2: Ticket for debounce implementation
• Stage-2a: On taking the slider to 100 percent, it should change into a button will marks the task as COMPLETED (check figma design which is linked above)

We need to have certain checks running on every PR and commits being pushed which will make sure that linting and build are going well.

For example, there could be something which breaks some page/pages/whole site if we get it merged (may happen that some user didn't test their code before pushing). If we had some sort of checks which run as soon as there are new PRs and new commits pushed, so that potential harm could be avoided.

And what could be these checks?

• lint: checks the linting style
• test: runs the tests
• build: checks if the build is passing

We have to setup CI using GitHub actions

Now looking at the form, we don't get which are the required fields

An asterisk in red would help a lot 🙂

Example:

If we pull the devtools window (the one which we get by clicking inspect element) all the way up, we see this problem:

The footer should behave like the way it is behaving here: https://status.realdevsquad.com/

Since the user will have the cookie already in the browser which has data provided by GitHub (github_id and github_display_name), we should be taking the github_id from there and use it to pre-fill the Github ID field and disable the user from changing it.

Sign up flow: Framer Link

On hovering the Upload button on profile page screen, cursor should change to pointer

Go to https://my.realdevsquad.com/profile
Browse an image from local system, hover on the Upload button and you'll understand that your cursor is not becoming a pointer

If you're confused, what's a cursor pointer, refer this doc: https://developer.mozilla.org/en-US/docs/Web/CSS/cursor

• Should show some message if there are no tasks in a particular task category:

In the /tasks page, we are showing the logged in user's tasks by task status like active, pending etc. Let's say the user doesn't have any active tasks, they are shown nothing, they might keep waiting, under the impression that something is loading here. That's a bad UX (user experience). We need to show some message like "There are no tasks here. Please look into some other categories 🙂"

• Unix timestamp needs to be converted to human readable date

Show read-only information of the user on profile page

Currently our lint script doesn't work on Windows, but works fine on Linux and MacOS.

Once the lint starts working for these operating systems, we could add linting in pre-commit hooks (not a part of this issue though). Refer issue #10

We need to send the data from the signup form

Once the user logs in to Github for the first time from any of the RDS apps (welcome/crypto/main page), the user will be redirected to this signup form.

Then the user will have the cookie set in for all the RDS subdomains.

We will need to use PATCH /users/self API to update the user's data once the user submits the form - this is one time process.
API contract: https://github.com/Real-Dev-Squad/website-api-contracts/tree/main/users#patch-usersself

Homepage looks unusually long here - https://my.realdevsquad.com/

Create our current user form on /signup route our 'my' app
Ensure that there are decent validations in place:

• Name should be string
• Username should have first name as prefix
• Email should have an @ and a .
• Phone number would be nice with a country code dropdown, but start with autofilling +91-, but let it be editable in case the user is not from India
• Allow social media names to be single string. If user pastes link, guide them with a helpful message
• Submit button should be only allowed once all validations pass
• Error messages should show up in a red line below the input, and the border of the input should also become red

We already have github id during the OAuth process. We should not let the user change it once they login using it

We don't need to run our tests on push
We are doing that in Github CI