Synchronize README and wireframe docs - #30
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ffda83557c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if (config.badges && config.badges.length) { | ||
| config.badges.forEach(function (entry) { |
There was a problem hiding this comment.
Normalize singleton
badges values before calling forEach
SF.rail.createCard now assumes config.badges is an array, but the new API shape also encourages simple badge entries such as a single string/object. In the one-badge case ({ badges: 'TEMPRA' } or { badges: { label: 'HOT' } }), this branch reaches config.badges.forEach(...) and throws, so the entire rail card fails to render. Coercing non-array inputs to a one-element array would make the new badge support safe for scalar configs as well.
Useful? React with 👍 / 👎.
ffda835 to
bc20f71
Compare
Closes #11.
Summary