Open bhoppers2008 opened 1 year ago
react-element-to-jsx-string
) doesn't display the component name but <No Display Name>
in some scenarios e.g. BorderLayout, BorderItem and FormField. See parseReactElement.js#L49-L76. Consider mosaic sandpack issue. Fixed by #2349./*#__PURE__*/ (0,react_jsx_runtime__WEBPACK_IMPORTED_MODULE_0__.jsx)(_ToastsExamples__WEBPACK_IMPORTED_MODULE_2__.InfoToast, {})}].concat((0,_swc_helpers_to_consumable_array__WEBPACK_IMPORTED_MODULE_4__._)(toasts)));}}>
or, Border Layout change radio doesn't change code. (@origami-z) This could be the result of transform code, where we just need to show original code, where also benefits users to copy paste. Consider mosaic sandpack issue. Fixed by #2349.SaltProvider_SaltProvider
in show code. Fixed by #2349.a="true"
v.s. b={true}
https://github.com/jpmorganchase/salt-ds/pull/2330initialVersion
needs to be re-checked. It's also not revealed on site?title
has mixed usages. Only index.mdx
should has string value, the other 3 mdx files should be $ref
Note the displayName issue (number 7) seems to be due to the components using arrow functions rather than named functions, so we should create a ticket to go though and update all components to use named functions. Updating FlowLayout to the following fixed that component for me:
export const FlowLayout: FlowLayoutComponent = forwardRef(function FlowLayout<
T extends ElementType = "div"
>({ children, ...rest }: FlowLayoutProps<T>, ref?: PolymorphicRef<T>) {
return (
<FlexLayout direction="row" ref={ref} wrap {...rest}>
{children}
</FlexLayout>
);
});
from
export const FlowLayout: FlowLayoutComponent = forwardRef(
<T extends ElementType = "div">(
{ children, ...rest }: FlowLayoutProps<T>,
ref?: PolymorphicRef<T>
) => {
return (
<FlexLayout direction="row" ref={ref} wrap {...rest}>
{children}
</FlexLayout>
);
}
);
- Clicking on the chevron in the side nav should only expand/collapse the item, not open the page at the same time.
I believe this'll be fixed when we replace the current vertical nav component (which comes from Mosaic) with our own, based on the NavigationItem
component.
Not sure there's much point trying to "fix" this in the Mosaic component now, given that we're due to replace it anyway.
FYI, I've opened an issue to note some additional functionality for the LivePreview
component (the thing that displays our component examples) that has been discussed in the past but never actually written down: #2348
A place to capture feedback on the docs template or the site page itself. Where are the challenges? Is there anything missing? Is it difficult to find a place for content you want to add? Etc...