Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Control the topic data field access with read-only flag in the extension_item_GET

Open
#352 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
api

Research direction

Start with the extension_item_GET definition and inspect how topic fields currently expose their identity and value. Determine the response location and semantics for a read-only flag that indicates whether the current user may modify each value; done means the API specification clearly defines this behavior.

Written by the indexing model from the issue text.

Description

Each topic field now has identity in addition to the value. We could add a read-only flag so that it is easy control whether the current user has the right to modify that value in a specific topic or not.

@jasollien to fill in more info, if needed.

Dominant language
No language data
Stars
239
Forks
67
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from buildingSMART/BCF-API

All issues in buildingSMART/BCF-API

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.