primefaces / primereact Goto Github PK

did that get left out?

Unable to create a TabView where the activeIndex is not the first, because the component uses the value from its state and ignores the value it receives in props.

We should use the componentWillReceiveProps lifecycle method to copy the value from component props to state.

If we focus on the chips input box then it should get the focus like any other input component.This can be replicated on showcase as well.

Just the same problem as with TabView.

As per the documentation the label is also clickable and toggles the checked state.But as of now the label doesn't toggle the checkbox state.

I installed and run the code, however, the styling is broken for most of the components.

There is small typo on SlotChar heading.It should be 'SlotChar' instead 'SlothChar' :)

The Button component unconditionally overwrites the type attibute to 'button' even if I want it to be 'submit'.

In contrast I can create an InputText with type attribute set to 'password'.

The autocomplete dropdown is not exactly aligned with input.This can be replicated on showcase with advanced feature.

If we use autocomplete by enabling multiple feature(i.e, multiple=true) then input should get the focus like other cases.This can be replicated on showcase as well.

I've created a package for 1.0.0-alpha2 using "npm pack" command, and the primeng.min.css is missing line.gif. The original file is Tree.css.

As per the documentation the label is also clickable and toggles the radio button state.But as of now the label doesn't toggle the radio button state.

If we click on the schedule event then dialog should appear with event details.This can be replicated on showcase as well.

The setup documentation has typos by pointing to PrimeNG instead of PrimeReact in many places.(Espeically import section)

PR: #8

If you select or click multiselect inputbox then it should get focused like any other input component.This can be replicated in showcase too.

Hello,
According to me defaultProps and propTypes as static members are nicer than assigning outside of the class. Do you have a specific reason to go like that?

The button components requires focus once there is a click action/operation.This issue is replicated for buttons with severity classes.This can be replicated on showcase.

Defines the orientation of the tree, valid values are 'vertical' and 'horizontal'.

The Dropdown's onChange event need to be invoked when there is a change in the value.If we select the same value twice then also this callback event is invoked.

I saw PR #5 out there.

Are there any plans on adding tests?

If you select or click dropdown inputbox then it should get focused like any other input component.This can be replicated in showcase too.

Currently the spinner controls are very small and difficult to do user actions.The width of the controls area need to enlarged.

The accordion tabs need to be toggled by clicking anywhere in the tab bar.As of now tabs content is not toggle-able on click of icons.This can be replicated on showcase.

Hi all,

Thank you for the good job. Just wondered if you have any plan to integrate unit tests for each component and so on?

Thanks

Baris

Theme files need to be converted from SASS to CSS files.To work with build from source, there is a need of documentation for SASS install or node-sass steps to notify users .