Skip to content

docs: fix build issue with example #995

docs: fix build issue with example

docs: fix build issue with example #995

Triggered via pull request February 28, 2025 14:09
Status Failure
Total duration 54s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
lint: examples/salty-ocean-model-comparison/src/index.tsx#L1
Run autofix to sort these imports!
lint: examples/salty-ocean-model-comparison/src/index.tsx#L25
Use an `interface` instead of a `type`
lint: examples/salty-ocean-model-comparison/src/index.tsx#L29
Use an `interface` instead of a `type`
lint: examples/salty-ocean-model-comparison/src/index.tsx#L52
Async arrow function has no 'await' expression
lint: examples/salty-ocean-model-comparison/src/index.tsx#L61
Unnecessary conditional, comparison is always true, since `"model" === "model"` is true
lint: examples/salty-ocean-model-comparison/src/index.tsx#L110
Unexpected any. Specify a different type
lint: examples/salty-ocean-model-comparison/src/index.tsx#L114
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
lint: examples/salty-ocean-model-comparison/src/index.tsx#L118
["OPENAI_API_KEY"] is better written in dot notation
lint: examples/salty-ocean-model-comparison/src/index.tsx#L125
["GROQ_API_KEY"] is better written in dot notation
lint: examples/salty-ocean-model-comparison/src/index.tsx#L155
["OPENAI_API_KEY"] is better written in dot notation
lint
Both node-version and node-version-file inputs are specified, only node-version will be used