facebook / facebook/astryx

[Bug] LayoutFooter Properties preview renders no working component

Open
#5,895 0 comments 0 reactions 0 assignees View on GitHub
bug good first issue
Dominant language
TypeScript
Stars
13.1k
Forks
1.1k
Avg merge
1d 14h
Merged PRs (30d)
669

Description

## Affected page

https://astryx.atmeta.com/components/LayoutFooter?tab=properties

## Steps to reproduce

1. Open the affected component page in Chromium 149.0.7827.55 on macOS.
2. Open the **Properties** tab.
3. Observe the preview before changing any props.
4. Exercise the available controls where applicable.

## Expected behavior

A visible footer region renders in a minimal Layout scaffold.

## Actual behavior

The preview stage is completely empty except for the Show code control.

No unrelated console or page errors were observed during the fresh-context reproduction.

## Diagnosis

The subcomponent has no child content or parent-layout playground wrapper, so its standalone region is empty.

The likely fix is local to `packages/core/src/Layout/LayoutFooter.doc.mjs` and/or its focused docsite preview coverage; it does not require a new public API or design direction. This is an atomic, independently closable slice of #2008.

## Acceptance criteria

- [ ] Add representative footer content and a minimal Layout playground wrapper.
- [ ] The preview renders a visible footer on first load.
- [ ] A relevant footer control such as divider or height produces an observable update.
- [ ] Add focused preview/data-extraction coverage.

Contributor guide

Open the contributing guide

Research direction

Start with packages/core/src/Layout/LayoutFooter.doc.mjs and reproduce the empty Properties preview at the affected LayoutFooter page. Inspect the focused docsite preview/data-extraction coverage, then verify that representative footer content, a minimal Layout wrapper, and a footer control update produce the expected visible result on first load.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation, frontend, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
82/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.