/dashboards/{dashboardID}/cells PUT - property viewID in Cell schema seems to be ignored
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- openapi, yaml
- Domain
- api
Research direction
Start with src/common/schemas/Cell.yml and the PUT /dashboards/{dashboardID}/cells endpoint, then compare the Cell viewID property with the ../cells/${cellID}/views API context. Confirm whether viewID is consumed or ignored, and document or implement the schema change needed so the specification matches the API behavior.
Written by the indexing model from the issue text.
Description
In the common schema Cell is a property viewID. I've tried to set erroneous values to this property and send it as part of a requestBody, however it seems to be ignored by the server. Does it still serve a purpose? Or since views are now handled by the ../cells/${cellID}/views context, can it be removed?
src/common/schemas/Cell.yml
type: object
properties:
id:
type: string
links:
type: object
properties:
self:
type: string
view:
type: string
x:
type: integer
format: int32
"y": # Quoted to prevent YAML parser from interpreting y as shorthand for true.
type: integer
format: int32
w:
type: integer
format: int32
h:
type: integer
format: int32
viewID:
type: string
description: The reference to a view from the views API.
- Dominant language
- Shell
- Stars
- 18
- Forks
- 9
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 1
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
- 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.
More from influxdata/openapi
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
influxdata/openapi#657 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
influxdata/openapi#653 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
influxdata/openapi#240 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
influxdata/openapi#636 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
influxdata/openapi#621 ·
All issues in influxdata/openapi
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
community-scripts/ProxmoxVE#17674 ·
Maintainers usually reply within 1 day
-
[Request]: Improve robustness and path resolution in ensure-hawkeye.shPossibly taken @denizguney claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/WindowsDeveloperConfig#139 ·
Maintainers usually reply within 1 day
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oSoWoSo/vOid_Community_repOsitory#248 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
collabnix/awesome-mcp-lists#157 ·
Maintainers usually reply within 1 day