fix:CascadeSelect missing some values in pt

[kl-nevermore]

Fix #5479

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
primereact	⬜️ Ignored (Inspect)	Visit Preview		Dec 2, 2023 3:42am
primereact-v9	⬜️ Ignored (Inspect)	Visit Preview		Dec 2, 2023 3:42am

[github-actions]

Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>.

[github-actions]

Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>.

[github-actions]

Thanks a lot for your contribution! But, PR does not seem to be linked to any issues. Please manually link to an issue or mention it in the description using #<issue_id>.

[melloware]

@kl-nevermore @Dalorzo I think this is mixing up cx with ptm? PTM only receives the values passed to it through its context and state

export interface CascadeSelectPassThroughMethodOptions {
    props: CascadeSelectProps;
    state: CascadeSelectState;
}

/**
 * Defines current inline state in CascadeSelect component.
 */
export interface CascadeSelectState {
    /**
     * Current focused state as a boolean.
     * @defaultValue false
     */
    focused: boolean;
    /**
     * Current overlay visible state as a boolean.
     * @defaultValue false
     */
    overlayVisible: boolean;
    /**
     * Current overlay attributeSelector state as a string.
     */
    attributeSelector: string;
}

It looks like you are passing the same values that would go to cx to the ptm?

[kl-nevermore]

I can't impl some styles in unstyled using pt if I can't get consistent values

example

// in classes can add style for active item,but pt can not 
  'p-cascadeselect-item-active p-highlight': activeOptionState === option

I referred to some comp like dropdown use ptm pass value to pt
Other components also have this problem
It should be necessary for ptm and cx to be consistent?
If this is correct, the types file should also be updated

[melloware]

That is a good question. It seems CX and PTM are definitely treated differently I am not quite sure why. And yes the Types would have to be updated that is what @Dalorzo has been helping with.

[melloware]

@kl-nevermore @Dalorzo see my PR fixing these issues:

#5507

So for PTM you always have 3 objects context, state, props

export interface CascadeSelectPassThroughMethodOptions {
    props: CascadeSelectProps;
    state: CascadeSelectState;
    context: CascadeSelectContext;
}

So for your examples above in passthrough you will use.

label - use context.label to get the labels

item - use state.grouped and state.active to determine if the item is active or in a group.

'list and sublist- now have the propercontextvalue which includes all API options like ripple andinputfilled` etc.