[Feature]:Should id param on useFunnel always be needed?

[bigsaigon333]

Package Scope

@use-funnel/core

Description

I want the id parameter on useFunnel to be optional, and I want the URL to remain as ?step=stepName without the id. prefix.

Currently, the id parameter is required, and it appears in the URL as ?id.step=stepName

My goal is to simplify this by skipping the id. and just using step as the name of the searchParams.

I’m only using one useFunnel hook on the page, so having just step in the URL should work fine for me.

Can you guys consider this feature?

const funnel = useFunnel<{ A: {}; b: {} }>({
//  id: '',    <--- I want id parameter to be optional!! and remains in th url ?step=A
  initial: { step: 'A', context: {} },
});

Possible Solution

No response

etc.

No response

[bigsaigon333]

I tried using useFunnel({ id: "" }), but the period (.) still remains in the URL as ?.step=A

[minuukang]

Because about sub funnel concept. it should be a unique id in component tree.

But your suggestion seems like a good enough need. We'll consider adding an option to customize it!

[manudeli]

If we make it optional and don't put in a separate id, how about using useId to internally use a unique value? I think it would be better if it lowers the onboarding hurdle for users.

[minuukang]

@manudeli But useId() is volatile, so refreshing in the browser will make the data unavailable!