Skip to content

Conversation

@jpuzz0
Copy link
Contributor

@jpuzz0 jpuzz0 commented Feb 20, 2023

What: Closes #7507

"scripts": {
"build:umd": "rollup -c --environment IS_PRODUCTION",
"clean": "rimraf dist",
"clean": "rimraf dist components layouts helpers next deprecated node_modules",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not pertain to this exact change, but something noticed when running clean, I believe these built sub-directories should be included.

"analyze": "yarn build:docs --analyze",
"build:docs": "pf-docs-framework build all",
"clean": "rimraf .cache public static/assets static/base.css src/generated/**/*.js",
"clean": "rimraf .cache public static/assets static/base.css src/generated/**/*.js node_modules",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When using a local version of the documentation-framework, it helps to clear out these node_modules, as sometimes not doing so leads to false-positives/negatives.

'FormFieldGroupHeader',
'FormFieldGroupHeaderTitleTextObject',
'FormContextProps',
'FormContextProviderProps',
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both of these types should probably be marked as beta, but there is no way to do so yet with the PF documentation-framework. The only use-case is an example called FormState, which is marked as beta, so hopefully that will suffice for now.

@patternfly-build
Copy link
Contributor

patternfly-build commented Feb 20, 2023

@jpuzz0 jpuzz0 force-pushed the feature/form-context branch 2 times, most recently from bb7f81c to 0b95e06 Compare February 20, 2023 18:16
Copy link
Contributor

@wise-king-sullyman wise-king-sullyman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neat! I just have a couple small nit things and one test I'm not sure about.

@jpuzz0 jpuzz0 force-pushed the feature/form-context branch from 7b7e044 to c606f44 Compare March 27, 2023 14:03
Copy link
Contributor

@kmcfaul kmcfaul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm just needs a rebase

@jpuzz0 jpuzz0 force-pushed the feature/form-context branch from c606f44 to 5afe1fb Compare April 12, 2023 18:53
@nicolethoen
Copy link
Contributor

Github wont let me merge this because it says there are still conflicts needing to be resolved?

@jpuzz0 jpuzz0 force-pushed the feature/form-context branch from c923234 to a0aa692 Compare April 13, 2023 23:52
@jpuzz0
Copy link
Contributor Author

jpuzz0 commented Apr 13, 2023

Github wont let me merge this because it says there are still conflicts needing to be resolved?

Yeah, looks like another PR merged today led to another conflict. I rebased and resolved that conflict just now.

@nicolethoen nicolethoen merged commit 45d2c7a into patternfly:v5 Apr 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FormContext - Add context for Form to manage input state

5 participants