Your first data view

Deprecated (5.x only)

This page applies to the 5.x line only (npm 5.1.x, branch 5.x). @ahoo-wang/fetcher-viewer is deprecated on npm (every version) and frozen there: existing functionality is maintained, with no new features. It is replaced by @ahoo-wang/wow-view-engine in the Wow repository (typescript/, wow.ahoo.me), on npm from Wow 9.2.0 (9.2.1 or later accepts fetcher 6). The two use different models and APIs, so migration requires adaptation.

Fetcher main ships no data-view component. Existing 5.x consumers build tables with the Ant Design Viewer below; new work targets @ahoo-wang/wow-view-engine (see wow.ahoo.me), or a new table can also compose React request state with the table component your application already uses.

Ant Design Viewer path

Start with the complete local Viewer example. It supplies a consumer installation, one complete component, the React entry and a run command. No server, authentication setup or Storybook fixtures are needed.

Follow its five actions: inspect the first page, change pages, sort Name, filter Active, then save and switch views. The row results change because the example application calculates the data and supplies it to Viewer.

Piece	Owner
Fields and available filters	Application's ViewDefinition
Page/condition/sort interaction	Viewer calls the application
Filtered, sorted, paged rows and total	Application's local calculation
Saved settings and success callback	Application's in-memory state
Permanent storage and access control	Your application and backend

Use the linked example's Storybook entry and browser check on the 5.x branch to verify the same behavior. It is the single executable source for this page; refreshing loses saved views. The optional server data monitor is outside this local example.

A single table may only need View. Use Viewer for a collection of views with application-owned loading and saving. Consider FetcherViewer only when your service implements its expected protocol; see the FetcherViewer reference.