salesforce / salesforce/design-system-react

Add RecordForm Component with Docked Footer Support

Open
#1,395 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

form mc-design-backlog needs-clarity
Dominant language
JavaScript
Stars
982
Forks
440
Avg merge
1d 21h
Merged PRs (30d)
4

Description

Since InlineEdit is going to be deprecated. The form editing pattern is a Popover/Edit icon button for single input fields and the SLDS Form Edit mode for multiple field forms.

I propose creating a <Form> component that wraps form elements and allows adding a Docked Form Footer. The following is a mockup. Docked Footer should always be paired with Read/Edit mode of forms.

01

Consumers would still need to update inputs from read only variants to base inputs themselves, but I'm open to suggestions. I would be difficult to pass a prop down into the inputs directly since they may be nested in formatting. This might be a place to use React's context?

The primary issue with Docked Form footer is that it might need to be fixed to the bottom of the page and not scroll.

I need additional input from stakeholders.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the SLDS Form Edit and Docked Form Footer references, along with the InlineEdit deprecation issue. Clarify the component API, Read/Edit behavior, context needs, and fixed-footer behavior with stakeholders before implementation. Done means the design and requirements are agreed and the component behavior is defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.