Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: added support to handle nooption #820

Merged
merged 3 commits into from
Sep 9, 2024

Conversation

sagardspeed2
Copy link
Contributor

@sagardspeed2 sagardspeed2 commented Sep 5, 2024

Describe your changes

added support to handle no record option

Screenshots [Optional]

Issue ticket number and link

Closes #710

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have added tests
  • I have added a changeset pnpm changeset add
  • I have added example usage in the kitchen sink app

Copy link

changeset-bot bot commented Sep 5, 2024

🦋 Changeset detected

Latest commit: fe4a5db

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@ensembleui/react-kitchen-sink Patch
@ensembleui/react-runtime Patch
@ensembleui/react-preview Patch
@ensembleui/react-starter Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

github-actions bot commented Sep 5, 2024

Visit the preview URL for this PR (updated for commit fe4a5db):

https://react-kitchen-sink-dev--pr820-710-handle-no-record-ewcjnzzj.web.app

(expires Mon, 16 Sep 2024 09:04:05 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 6267897ade2ba783b6db70a53a60fc3946d625e9

Comment on lines 151 to 162
// handle not found content renderer
const notFoundContentRenderer = useMemo(() => {
const notFoundContent = values?.notFoundContent;

if (!notFoundContent) {
return null;
}

return isString(notFoundContent)
? notFoundContent
: EnsembleRuntime.render([unwrapWidget(notFoundContent)]);
}, [values?.notFoundContent]);
Copy link
Contributor

Choose a reason for hiding this comment

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

what would be default value?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@anserwaseem check again please, I added default value

@sagardspeed2 sagardspeed2 merged commit ab37ee9 into main Sep 9, 2024
3 checks passed
@sagardspeed2 sagardspeed2 deleted the 710-handle-no-record-option branch September 9, 2024 10:02
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.

Support option on Search widget to handle empty results behavior
2 participants