Jules Comments - Answer Overflow

Jules

Explore posts from servers

SSolidJS XXata

Posts Comments

SSolidJS

•Created by aryzing on 10/20/2023 in #support

What's the most idiomatic way of forwarding an onClick event handler?

Yeah strangely it is - I don't know why I don't see the same error, am using plugin:solid/typescript

13 replies

SSolidJS

•Created by Jules on 10/20/2023 in #support

createSelection() primitive odd behaviour in contentEditable div's

because the comlpexity can be skipped if all you need is selectionStart and selectionEnd to achieve the use case I am working with but that somehow doesn't exist on a div object with contentEditable={true}

9 replies

SSolidJS

•Created by Jules on 10/20/2023 in #support

createSelection() primitive odd behaviour in contentEditable div's

you mean the browser API? the complexity makes sense but why it differs needlessly between elements and browsers is what is frustrating to me. Though I suppose to some degree all web APIs do

9 replies

SSolidJS

•Created by Jules on 10/20/2023 in #support

createSelection() primitive odd behaviour in contentEditable div's

oh wow I wasn't expecting the author of this primitive to stumble upon this - I am willing to help out with a fix, I assume it wasn't intended behaviour but rather just an edge case. Do you have any ideas better than walking the DOM to determine whether the selection spans multiple Nodes? I was getting frustrated with my attempts since it seems like there should just be a browser API for this......

9 replies

SSolidJS

•Created by aryzing on 10/20/2023 in #support

What's the most idiomatic way of forwarding an onClick event handler?

I use this method with no trouble, or linter errors, thus far, though I have no idea if it is the most idiomatic solution:

export const Button = (props: {
  class?: string;
  onClick?: (event: MouseEvent) => void;
  children?: JSX.Element | string;
}) => {
  // much of the functionality omited for brevity
  return (
    <button onClick={props.onClick} class={cn('btn', styles, props.class)}>{props.children}</button>
  );
};

export const Button = (props: {
  class?: string;
  onClick?: (event: MouseEvent) => void;
  children?: JSX.Element | string;
}) => {
  // much of the functionality omited for brevity
  return (
    <button onClick={props.onClick} class={cn('btn', styles, props.class)}>{props.children}</button>
  );
};

13 replies

SSolidJS

•Created by dmayo2 on 10/17/2023 in #support

direct link?

Can we take a look at your vite.config.ts? that would be helpful in diagnosing your issue, also any logs during the Netlify build process or http logs for the route you're trying to hit. In general though, @bigmistqke is trying to get you setup with the vite adapter for Netlify so that your build is done correctly and thus Netlify's servers will be looking in the place where your build is outputted. Here is an example config, and basically what yours should look like:

import solid from "solid-start/vite";
import { defineConfig } from "vite";
import netlify from "solid-start-netlify";

export default defineConfig(() => {
  return {
    plugins: [
      solid({
        ssr: true,
        adapter: netlify({
          edge: true,
        }),
      }),
    ],
  };
});

import solid from "solid-start/vite";
import { defineConfig } from "vite";
import netlify from "solid-start-netlify";

export default defineConfig(() => {
  return {
    plugins: [
      solid({
        ssr: true,
        adapter: netlify({
          edge: true,
        }),
      }),
    ],
  };
});

17 replies

SSolidJS