core/element: a strict computePivot, and one name for the view type

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, react

Research direction

Read the computePivot API and view type exports in pivotkit-react and pivotkit-element, along with docs/versioning.md. Decide how unknownField errors should affect computed rows and which view type name should be shared, then document and implement the agreed public API changes with coverage for both packages.

Written by the indexing model from the issue text.

Description

area:core enhancement

Two proposals from the developer-docs round (#512), both new public interface, so they need a decision:

  • computePivot keeps all rows when a filter names an unknown field and reports unknownField as an error issue. A host that does not read the issues trusts wrong numbers. Option: a strict option, or a helper that throws on error issues.
  • pivotkit-react calls the view type ViewInput, pivotkit-element PivotView. Option: export one name from both packages (an alias), with the other deprecated per docs/versioning.md.
Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
3h 21m
Merged PRs (30d)
250

Getting set up

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 eizedev/pivotkit

All issues in eizedev/pivotkit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.