ecellnitrr / teesco-app Goto Github PK

server: http://159.65.158.103:5555/docs/

Describe the solution you'd like

1. Connect orgslist widget to the API
2. Cover error handling for all the cases provided in the API docs.
3. Try creating a user and add that user to a few orgs with the help of swagger API. So you can have easier time developing.

Is your feature request related to a problem? Please describe.

In auth feature. name functions and variables appropriately
3 subscreens:

1. enter mobile number (basic validation and basic UI)
2. an otp will be received on that number, screen for user to enter it in a textfield (6 digits asof now.)
3. if otp is correct, new and confirm password fields. appropriate validations required
4. if everything goes perfect -> log him in directly.

Describe the solution you'd like
build the query section screen with below widgets:

1. query_message widget which can be customized with the following inputs to the constructor
   1. messageId
   2. message
   3. timestamp
   4. authorName (if the messge is sent by the logged in user then no need to show the name. also message sent by the loggedin_user is on the right and others will be on the left)
2. query_input which should support multiline
3. submit_query which is the button which sends the query to the backend.

Is your feature request related to a problem? Please describe.
No. It is the basic requirement of the app.

Describe the solution you'd like

1. Page to enter the name, tagline and icon for the organisation.
2. User can use pick image from the local device gallery.

Additional context

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

server: http://159.65.158.103:5555/docs/

Describe the solution you'd like

1. Connect create org widget to the API
2. Cover error handling for all the cases provided in the API docs.

Is your feature request related to a problem? Please describe.
Currently, user have to log in to see the home screen every time.

Describe the solution you'd like
When a logged-in user opens the app the user should be automatically taken to orgs list screen.

Describe alternatives you've considered
Ideally last opened org should be open but since we have not wired up the org list api yet #36 it is a good enough fix for now.

Is your feature request related to a problem? Please describe.
Complete Login functionality.

Describe the solution you'd like

1. Wire the login API to the login UI built in #18
2. Make use of bloc and flutter http package.
3. Add flutter http to pubspec.yaml
4. No need to write tests

login screen states:

1. initial_state
2. loading_state
3. login_success
4. login_failure

sideeffects:

upon login_success:

1. save the auth token to shared preferences
2. navigate to home screen

Is your feature request related to a problem? Please describe.
In the current scenario, the first screen that the user will see when the app is opened is "login screen"

Describe the solution you'd like

1. This had to attempted only after #17 is solved.
2. create login screen UI - email, password and login button (for now its enough)
3. Make it as the first screen to be rendered when the app is opened.

Is your feature request related to a problem? Please describe.
As a user, I should be able to see the details of the org I am a member of.

Describe the solution you'd like

1. The social media icons are not needed in the beta release of our app. (as in the above img)

dev server live at: http://159.65.158.103:5555/docs/

Describe the solution you'd like

1. wire the create group screen to API

Additional context
Since #36 and #35 aren't solved yet we have to mock the needed functionality to get the org_id needed for this API call. So for testing purposes with the help of swagger docs

1. create a user
2. create a org with the user
3. hardcode the group list API in the app
4. while making the PR put user credentials in the description so we can test the PR.

Is your feature request related to a problem? Please describe.
As an admin of the org I should be able to create groups.

Describe the solution you'd like

1. Create the group create screen UI.
2. PermissionList widget should be dynamic. Should render permissions from a dictionary. Key=permission name, value=boolean.

Is your feature request related to a problem? Please describe.
It is great to add caching as it will decrease testing time significantly.

Describe the solution you'd like
Add logic to check whether flutter exist in the cache and stop travis from cloning flutter repo unnecessarily.

Is your feature request related to a problem? Please describe.
PR description is not provided properly by the contributors when creating the PR.

Describe the solution you'd like.
Create a PR template.

Describe the bug
Custom Errors classes have been created and caught where Exceptions are to be created and caught.

To Reproduce
Its a semantic bug, cannot be produced.

Expected behavior
An Exception in Dart should be thrown for regular, expected program flow and is intended to be caught, whereas An Error in Dart should be thrown for unexpected program flow and should not be caught but addressed by the programmer. So, Instead of extending Error, we should implement Exception.

dev server live at: http://159.65.158.103:5555/docs/

Describe the solution you'd like

1. wire the group list screen to API

Additional context
Since #36 and #35 aren't solved yet we have to mock the needed functionality to get the org_id needed for this API call. So for testing purposes with the help of swagger docs

1. create a user
2. create a org with the user
3. hardcode the group list API in the app
4. while making the PR put user credentials in the description so we can test the PR.

Is your feature request related to a problem? Please describe.
As an admin of the org, I would like to view the list of groups under my Org.

Describe the solution you'd like

1. create groups list screen UI.
2. The numbers on the side indicate no of members in that group respectively.

Is your feature request related to a problem? Please describe.

Folder structure: features -> auth. A single screen with email, password, login buttons along with forgot password and signup redirects

Describe the solution you'd like

1. email and password fields with appropriate validations
2. api handling functions
3. dummy redirects

Is your feature request related to a problem? Please describe.
This custom notification is a core functionality of our app. It will be good to prototype it at the beginning so that we can understand the limitations clearly.

Describe the solution you'd like

1. while the app is opened pin this notification to the notification panel.
2. while the share button is pressed open https://ecell.nitrr.ac.in/ in the browser
3. while the screenshot button is pressed => close notification bar => take a screenshot.

server: http://159.65.158.103:5555/docs/

Describe the solution you'd like

1. Connect signup widget to the API
2. Cover error handling for all the cases provided in the API docs.

Is your feature request related to a problem? Please describe.
We a project structure in order to effectively work on the project.

Describe the solution you'd like
Create the folder structure as per the meeting and slack discussion

Describe the bug
remove unwanted packages in pubspec
dependencies to remove :-

• chopper: ^3.0.2
• freezed_annotation: ^0.7.1
• flutter_bloc: ^3.2.0
• dartz: ^0.8.9

dev-dependencies to remove :-

• chopper_generator: ^3.0.4
• freezed: ^0.10.6

Expected behavior
packages should be added as and when required by the code and not before hand

Is your feature request related to a problem? Please describe.
We need a navigation bar to go to different screens

Describe the solution you'd like

Add a bottom navbar with 5 routes (icons need not be final)

1. org_info
2. tasks
3. home
4. query section
5. leaderboard

Create folder structure for all the above screens. And add a simple placeholder widget for all the above routes.

Is your feature request related to a problem? Please describe.

Folder structure: features -> auth. A single screen with name, email, institution, phone number(max length 10), country code(max length: 6) and password, signup buttons along with forgot password and login redirects
Describe the solution you'd like

1. all fields with appropriate validations (check the internet for validations)
2. api handling functions
3. dummy redirects

Is your feature request related to a problem? Please describe.

In auth change password feature main features are:

1. a : User enters his old password
2. b : Forgot password option is is available on the screen
3. b : An OTP is send if user clicks on forgot password and a screens pops up asking for OTP along
   with a resend OTP option with timer.
   2 : Enter the new password and confirms it

Screens and subscreens to be made:

1. Enter old password + forgot password option
   2 Enter new password + Confirm new password
   3 Forgot password(should be made as dynamic as possible)

Is your feature request related to a problem? Please describe.
As an admin of the org I would like to view the members of the groups under the org.

Describe the solution you'd like

1. create group members list screen UI
2. should be alphabetically ordered similar to a contacts app.
3. Divided into alphabetic sections

Is your feature request related to a problem? Please describe.
No. It's a Issue to provide registration ui feature

Describe the solution you'd like
The UI would be a single dart file :
Standard form with feature to validate it
Optional phone number feild
Required denoted by red *

Describe alternatives you've considered
Aside from Dribble UI, NA

Additional context
Screenshot would be added later

Is your feature request related to a problem? Please describe.

normal org info on left
org info for org admin in on the right

Describe the solution you'd like

1. The screen when mounted checks "what type of member is the current user in the current org". If the user is admin the screen should have show the special options as on the right side screen above. Until the needed setup is done find a way to mock this functionality.
2. add placeholder screen for statistics, invite, certificate, lb settings.
3. upon clicking the button the respective screen should be pushed into view.
4. no need to create an entirely new screen! just extend the current screen.

Describe the bug
Due to PR #32 and #30 , Two Organisation List Screen have been created.

Expected behavior
There should be only one Organisation List Screen.

How to Solve the bug
Delete the screen created in PR #32 and make changes to the routes created in PR #32 . The screen created in PR #30 must be linked with the home button of the navBar!

Screenshots

Is your feature request related to a problem? Please describe.
No. It is a basic requirement for the app.

Describe the solution you'd like
This feature will show the user the list of organisations of which he is a part.

Describe alternatives you've considered
It would be a simple list with each card holding a thumbnail image of the organisation, name of the organisation and user's assigned designation in the organisation.

Additional context

Describe the solution you'd like
Create edit org screen UI in which the user will be able to change

1. cover pic
2. org profile pic
3. org title, tagline and about

Is your feature request related to a problem? Please describe.
As a volunteer to the org, I should be able to able to have a look at the leaderboard.

Describe the solution you'd like

1. Create Leaderboard screen UI
2. the number on the left of the title indicates the user's points!
3. the first 3 people show have a gold, solver and bronze medal badge near their avatar. similar to