Skip to content
This repository was archived by the owner on Jul 9, 2025. It is now read-only.

feat: Align with the new design in form for inline error display#1683

Merged
a-b-r-o-w-n merged 12 commits intomasterfrom
julong/validation
Dec 4, 2019
Merged

feat: Align with the new design in form for inline error display#1683
a-b-r-o-w-n merged 12 commits intomasterfrom
julong/validation

Conversation

@alanlong9278
Copy link
Copy Markdown
Contributor

@alanlong9278 alanlong9278 commented Dec 2, 2019 •
edited
Loading

Description

Align with the new design in form for inline error display

Discussion

  • Show detail error message.(Now the error message is fixed)
  • Notification level. (Now only show error message, but notification message has 2 levels in notification page: warninig & error).

Task Item

closes #1623

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Code refactor (non-breaking change which improve code quality, clean up, add tests, etc)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Doc update (document update)

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have functionally tested my change

Screenshots

validation

a-b-r-o-w-n
a-b-r-o-w-n suggested changes Dec 2, 2019
View reviewed changes
Copy link
Copy Markdown
Contributor

@a-b-r-o-w-n a-b-r-o-w-n left a comment

Choose a reason for hiding this comment

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

How does this scale to all other form fields? We are not surfacing errors outside of the expression widget, but what happens when we do?

Comment thread Composer/packages/extensions/obiformeditor/src/Form/fields/PromptField/PromptSettings.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/fields/PromptField/PromptSettings.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/widgets/ExpressionWidget.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/widgets/ExpressionWidget.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/widgets/ExpressionWidget.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/widgets/ExpressionWidget.tsx Outdated
Comment thread Composer/packages/lib/code-editor/src/RichEditor.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/ObjectFieldTemplate/styles.css Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/fields/PromptField/PromptSettings.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/widgets/ExpressionWidget.tsx Outdated
@a-b-r-o-w-n
Copy link
Copy Markdown
Contributor

a-b-r-o-w-n commented Dec 2, 2019

Also, I didn't see anything to handle lint warnings. The spec is that we display an error if present, then a warning.

a-b-r-o-w-n
a-b-r-o-w-n suggested changes Dec 3, 2019
View reviewed changes
Comment thread Composer/packages/extensions/obiformeditor/src/Form/widgets/ExpressionWidget.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/widgets/ExpressionWidget.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/widgets/ExpressionWidget.tsx Outdated
Comment thread Composer/packages/lib/code-editor/src/RichEditor.tsx Outdated
Comment thread Composer/packages/lib/code-editor/src/RichEditor.tsx Outdated
Comment thread Composer/packages/extensions/obiformeditor/src/Form/fields/PromptField/PromptSettings.tsx Outdated
@boydc2014 boydc2014 mentioned this pull request Dec 4, 2019
Closed
7 tasks
@github-actions
Copy link
Copy Markdown

github-actions bot commented Dec 4, 2019

Coverage Status

Coverage decreased (-0.03%) to 41.001% when pulling c8f95dd on julong/validation into 730433c on master.

@a-b-r-o-w-n
Copy link
Copy Markdown
Contributor

a-b-r-o-w-n commented Dec 4, 2019

Note: What this change does not do is surface errors for any arbitrary field in the form. Only LG, LU and expression errors are surfaced right now.

@a-b-r-o-w-n a-b-r-o-w-n merged commit 997df62 into master Dec 4, 2019
@a-b-r-o-w-n a-b-r-o-w-n deleted the julong/validation branch December 4, 2019 23:06
@cwhitten cwhitten mentioned this pull request Dec 4, 2019
Closed
@a-b-r-o-w-n a-b-r-o-w-n mentioned this pull request Dec 11, 2019
Merged
@a-b-r-o-w-n a-b-r-o-w-n mentioned this pull request Dec 11, 2019
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@boydc2014 boydc2014 Awaiting requested review from boydc2014 boydc2014 is a code owner

@cwhitten cwhitten Awaiting requested review from cwhitten cwhitten is a code owner

1 more reviewer

@a-b-r-o-w-n a-b-r-o-w-n a-b-r-o-w-n approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@alanlong9278 @a-b-r-o-w-n @cwhitten