New to Rust? Grab our free Rust for Beginners eBook Get it free →
Building a Grid Interface with FeatherJS

When service records need to be found and changed, a table can present them in rows and columns. A Feathers grid interface connects that browser table to a Feathers service, which handles data rules and database access.
In this piece, I’ll show how to define the row fields and connect the grid to the service over REST.
TL;DR
A Feathers grid interface pairs a browser-side table with a Feathers service that validates and persists each change.
- Let the grid display, search, and edit rows.
- Let the service own data rules and database access.
- Require authorization and validation before accepting writes.
What is a Feathers grid interface?
A Feathers grid interface presents service records in rows and columns, with controls for finding and changing them.
The grid handles editing and feedback, while the service applies rules and a database adapter stores records. Feathers exposes services through REST for browser clients.
The original example paired jsGrid with Feathers and Sequelize. Current guides cover services, schemas, hooks, and adapters.
How to build a Feathers grid interface step by step
Begin with one resource, such as contacts, and decide its fields and permissions before connecting a table.
Step 1: Create the Feathers application and service
Use the Feathers CLI to scaffold the application, then add a service for the resource and connect it to a supported database adapter. The grid calls that service.
Step 2: Define the row contract
Choose fields such as an ID, name, and address. Keep the primary key available to identify a row during updates and removals.
Map table operations to service methods: find loads rows, create adds one, patch changes selected fields, and remove deletes by ID. Use patch for inline edits so unchanged fields stay intact.
Step 3: Expose the service over REST
Configure Feathers REST and serve the page from the application or an allowed origin. The grid loads the service collection and sends saves or removals to the matching service method.
Define the request and response shape before writing callbacks. A list returns rows and, when paginated, a total count.
Create sends editable fields, update identifies a row and changed values, and delete identifies the selected row. These are service integration requirements.
Step 4: Connect the grid and show results
Configure the data-loading callback to call the service and map records into columns. Match editable columns to accepted fields. Keep identifiers and audit fields read-only.
After a write, refresh the row or use the returned record. On failure, keep the edit visible and show the service error. Build list, add, edit, and remove before bulk actions.
Data and interface issues to handle
Enforce data rules on the server because browser controls can be bypassed. Feathers hooks and schemas validate data and queries. Authentication and authorization decide whether a user may write a record.
| Case | What can go wrong | Handling |
|---|---|---|
| Invalid cell | Client sends a value outside the field rules | Validate at the service and return a useful error |
| Large collection | Loading every row increases response size | Use bounded pages and a stable sort key |
| Concurrent edit | A later save overwrites another user’s change | Use version or updated-time checks where needed |
| Restricted record | A user can guess another row’s ID | Authorize service access by identity and record |
Keep database credentials and OAuth secrets out of browser code. The target page’s CentOS 7.5 and shell setup is dated. Feathers v5 changed SQL integration guidance, so follow the current CLI and documentation rather than its 2018 setup commands.
NN/g describes column, modular, and hierarchical layouts. A record table benefits from consistent columns and responsive sizing. Consider horizontal scrolling or fewer mobile columns on narrow screens.
Conclusion: keep the grid thin
Keep validation, authorization, and persistence in the Feathers service. The interface can focus on displaying rows and making edits clear.
For next steps, read the Feathers quick start and its hooks guide. CodeForGeek’s Node.js framework overview gives broader context, and its FeathersJS and MariaDB tutorial covers a related database task.
FAQ
Common questions about connecting a data grid to Feathers.
Can Feathers expose a grid’s data as REST?
Yes. Configure the REST transport to expose Feathers services over HTTP, then have the grid call the service methods.
Should the grid validate edited values?
The grid can provide immediate feedback, but the Feathers service must validate incoming data because clients are not trusted.
Can a grid use SQL storage?
Yes. Connect the Feathers service to a supported SQL adapter and keep database access on the server.




