Removed outline and task info from project/id endpoint

[Sujanadh]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Issue

• Fixes UX: remove task info from projects/<id> endpoint, call separately #935

Describe this PR

This changes removes the inherited ProjectBase schema model from ReadProject where only required fields are defined which excludes outline_geojson and project_tasks.

Response

{
  "id": 54,
  "odkid": 1817,
  "author": {
    "username": "Sujan Adhikari",
    "id": 18427944
  },
  "project_info": {
    "name": "testing sujan ",
    "short_description": "a",
    "description": "a"
  },
  "status": 2,
  "xform_title": "buildings",
  "hashtags": [
    "#FMTM"
  ],
  "organisation_id": 1,
  "project_uuid": "f27c2c4d-4338-41a2-bacc-0945a23afb38",
  "location_str": "Kathmandu,Nepal"
}

Checklist before requesting a review

• 📖 Read the FMTM Contributing Guide: https://github.com/hotosm/fmtm/blob/main/CONTRIBUTING.md
• 📖 Read the FMTM Code of Conduct: https://github.com/hotosm/fmtm/blob/main/CODE_OF_CONDUCT.md
• 👷‍♀️ Create small PRs. In most cases, this will be possible.
• ✅ Provide tests for your changes.
• 📝 Use descriptive commit messages.
• 📗 Update any related documentation and include any relevant screenshots.

[optional] What gif best describes this PR or how it makes you feel?

[spwoodcock]

It's fine to remove the tasks from the response on the backend, but that's a tiny part of the task in issue #935.

Most of the edits are on the frontend, where we need to load the project info first, then progressively load in task data as it's returned.

• The basic implementation needs coordination with the backend and frontend changes.
• A more complex implementation may require testing how to load in the task data progressively as it's returned, perhaps using something like StreamingResponse.

[Sujanadh]

Oh okay. Then fetching data in chunks rather than all at once in frontend must be the desired behaviour?

[spwoodcock]

Possibly! It's probably not worth optimising for now. Only the basic version is necessarily, then we can improve later.

[spwoodcock]

Closing for now - we will come back to this and coordinate with the frontend.