Implementation FPCV-19: Extend project API to consider "calculated values"

View differences

Regular project attributes show up under `v3/projects` (and other project endpoints) as follows:

```text
// Example: integer project custom field with ID 17
// field is disabled
// nothing to show...

// field is enabled, but has no value set
"customField17": null

// field is enabled and value is set to 32
"customField17": 32
```

Calculated values should behave like regular custom fields in that they display their calculated value there.

<br>

The administrative configuration of all project attributes is visible via `v3/projects/schema`. There, the API should recognize calculated values and make their formula available for read-access.

Open question: what about write access?

Back

Content

View differences