Versions Compared

Old Version 8

changes.mady.by.user Unknown User (zl942)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (zl942)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Contact info

Elizabeth Johnson | elj54@cornell.edu

...

Regarding demographics and the summary demographics

...

: served APIs are ONLY implemented as

...

middle-ware in the backend-offline repo. 

  • Code Block
    `/api/getSurvey/SV_2hHGHXngHMfsIyF`. 

The original GitHub repo has been split into 4 repos for 4 subteams. There were some issues building and running dashboard backend code in SP22, so the dashboard team decided to create a new repo and deploy their API using AWS Chalice. 

Their API serves for the demographics and summary demographics tab, all other APIs for the dashboard still rest at the repo called backend-offline. 

The building and running issue of backend-offline has been fixed, dashboard backend teams should be able to build and run the code later on. But having codes everywhere is bad for source control, so it would be nice if the dashboard backend team in the future could migrate codes into one place.

SubteamRepo link
Frontend

...

(mobile)https://github.com/DIAPER-Project/frontend-mobile
Frontend-webhttps://github.com/DIAPER-Project/frontend-web
Backend-online (mobile)https://github.com/DIAPER-Project/backend-online

Backend-offline (dashboard)


https://github.com/DIAPER-Project/backend-offline

Let us know via Slack if you need an access invite.

Note

Please make new changes under these new repos.

...

Implementation flow: 

  1. 📖 Understand the project structure: This initial step ensures you have a clear understanding of the existing codebase, project architecture, and dependencies, which is crucial for effective implementation.

  2. 🎨 Implement the feature: You focus on developing the new feature, following best practices, and ensuring it meets the project's requirements and specifications.

  3. 🏭 Reconstruct the implementations to achieve scalability and readability by decoupling the UI and Logic: After the implementation, refactor the code to separate the user interface (UI) from the business logic. This decoupling enhances code maintainability, scalability, and readability.

  4. 🙋 Start a Pull Request & Review request to the admin: Submit your changes through a pull request, inviting the project admin and team members to review your code. This step ensures that your implementation is scrutinized for quality, adherence to standards, and potential issues.

  5. 🧰 Fix highlighted issues: Address any feedback or issues raised during the code review. This collaborative process helps to catch bugs, improve code quality, and ensure the feature integrates smoothly with the existing codebase.

  6. ✅ Merge: Once all issues are resolved and the code review is approved, merge your changes into the main codebase. This final step deploys your feature and makes it available for use in the project.

Do not push any commitment to the master branch without authorization.Â