hackforla / hackforla/knowledgebase

API: Design for API for Assets and Asset Groups

Open
#38 0 comments 0 reactions 0 assignees View on GitHub
category: table complexity: large dependency draft feature: table: asset milestone: missing role: back end dev size: 3pt
Dominant language
Python
Stars
2
Forks
5
PR merge metrics
No merged PRs in 30d

Description

### Overview
As a BOP or Toolkit user, I want to be able to view Assets and Asset Groups

### Action Item as
- [ ] Document API specs for Asset and Asset Groups
- [ ] Based on the spec, break down into additional issues
- [ ] Spec includes separate APIs for Assets and Asset Groups
- [ ] Spec includes ability to query by all fields, unless determined not necessary

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the repository's existing API conventions and the current Asset and Asset Group models or entry points. Document separate APIs, query behavior for available fields, and any decisions about fields that should not be queryable. Break the resulting specification into follow-up issues and confirm every checklist item is addressed.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.