VLADI, tranquilo, no podemosfallar, tengo mi baraja de lasuerte

R-E-S-P-E-C-T, take care of T-C-B

'set-cookie': response.headers.get('set-cookie')

If you do need to passthrough your mydomain.com cookies to a thirdparty.com domain, you can technically already do that now by implementing it as an endpoint and calling fetch('/my-endpoint')

I don't really want to re-implement all of my api endpoints to make this work. Is there a way to "mask" the thirdparty endpoints to pass through the cookies?

allow <slot> to be part of a slot

I want to make some add-ons or wrappers on components e.g BigButton.svelte <script> import Button from './Button.svelte' </script> <Button fz="16" h="64" {...$$props}> <slot slot="prepend" name="prepend" /> <slot /> <slot slot="append" name="append" /> </Button>

Related to #1824, can do <svelte:component this={Bar}> <slot></slot> <slot name="header" slot="header"></slot> </svelte:component> <script> import Bar from './Bar.svelte'; </script> as a forwarding workaround

I am trying to implements this usecase (a generic lazy loader component which forwards slots/events to the "real" component).

In 3.29.0 you can now use <slot slot='...'> to forward slots into a child component, without adding DOM elements.

Would love to see passthrough slots to create superset components, for example Table and TableWithPagination (table slots for TableWithPagination could be passed through to Table).

All standard UI events are forwarded on components, input events ("input" and "change") are forwarded on input components, and all MDC events are forwarded.

You can add props to lower components and elements with things like input$maxlength="15".

You can add actions to the components with use={[Action1, [Action2, action2Props], Action3]}.

All standard UI events are forwarded.

class: '' - A CSS class string.

use: [] - An array of actions and/or action/property arrays.

In a later major, we'd stop extracting key from props and therefore props is now just passthrough.

Solid supports spread operator on native elements and Components.

There are usually very little amount of properties that a component relays on

The point of the feature is to not rely on the third-party author of the child component to add a prop for every action under the sun. Rather, they could just mark a recipient for actions on the component (assuming there is a viable target element), and then consumers of the library could extend the component using whatever actions they desire.

They don't need to add a prop for every action. The action itself can be passed in as a prop. <script> export let action; </script> <div use:action>whatever</div> The argument for the action can be another prop or can be part of the same prop.

Part of the functionality that is returned are event handlers. I'd like to avoid needing to manually copy the events over one by one so the hook implementation details are hidden.

If you want to listen to an event on some deeply nested component, the intermediate components must forward the event.

We should also allow passing unrecognised props to the rendered component. eg: tabindex might be required on some instances of a component, and not all. Why should developers have to add tabindex support to their components just that it may potentially be used

You could do something like this instead while maintaining complete control of where different props go. <div class="wrapper> <div {...$$props} > ... </div> </div>

All of the components should allow passing MUI configuration properties to them so that they can be easily customized. In the case of RFF and MUI components with deeply nested structures of multiple subcomponents, you can pass the properties in with sepecial top level properties. This is very hard to document fully without making a mess, so please refer to the source code and demos for examples.

propsToPass

PASSTHROUGH_PROPS

For example, if you were to add a className prop to the top or bottom <div> in the above demo, the <List> component would remove it in place of the top or bottom class. You can see this in the following example, where I’ve added the highlight class to the top two rows, but only the middle row is actually highlighted.To fix this, you’ll need to append a string to the className instead of replacing it.

It makes sense that the incoherent render would not be committed to browser and that it would not have any consequences most of the time. But that means that you render logic must be ready to manage incoherency between props and states without crashing. E.g. a list of resource ids in props that doesn't match a list of http requests from a previous id list in the state could lead to weird situations. This is a worry that didn't exist in class components.

Inner RefSome components are passed an innerRef property to facilitate for internally managed behaviour within the base select. This should be assigned to the ref property of the relevant dom element. i.e.const CustomOptionComponent = ({ innerProps, innerRef }) => (<div ref={innerRef} {...innerProps} />) Inner PropsAll functional properties that the component needs are provided in innerProps which you must spread.

An Open Letter to Marc Andreessen and Rap Genius