Define data source on column definition
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Sometimes you need a calculated value or request another endpoint for a value. So we should provide a way how to do that. One approach would be to add a new column type for calculation. But with that we have to define how the results will be represented, means which column type (checkbox, number, text, ...). How can we bring that together in a very, very intuitive way?
I suggest it's better to provide a selection for the data source in the "normal" column definition. By default the values come from the web form or API.
Data source -> Data transformation (mapping to needed formats) -> Representation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by examining the existing column-definition flow and how values from web forms and APIs are handled; done requires an agreed design for data sources, transformations, and representations before implementation can be scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100