Skip to content

handle error in creatable multi select text input #3814

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

Closed
wants to merge 2 commits into from

Conversation

ankush29
Copy link

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Oct 17, 2019

💥 No Changeset

Latest commit: 3487cd0

Merging this PR will not cause any packages to be released. If these changes should not cause updates to packages in this repo, this is fine 🙂

If these changes should be published to npm, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

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

@JedWatson
Copy link
Owner

Hey @ankush29 thanks for the PR

As per my comment on #3813, could you help by providing more context on this please:

  • what bug are you fixing?
  • how can we reproduce the bug?
  • why this particular fix solves the bug, and
  • what other effects could arise from the change

You can launch any example in codesandbox to help quickly provide a reproduction case for the issue you're fixing.

@bladey bladey added the awaiting-author-response Issues or PRs waiting for more information from the author label May 26, 2020
@bladey bladey added the pr/bug-fix PRs that are specifically addressing a bug label Jun 4, 2020
@bladey
Copy link
Contributor

bladey commented Jun 24, 2020

Hi @ankush29, I wanted to check in with you and the status of this PR.

As per @JedWatson's comments - if this PR is still relevant, can you please provide more context.

We're triaging issues at the moment to sustain the project going forward and closing old and inactive PRs.

@bladey
Copy link
Contributor

bladey commented Jun 29, 2020

Hi @ankush29, I'm now going to close this PR due to inactivity. If you have any further feedback, please do let me know and we'll re-open and assess, thank you!

@bladey bladey closed this Jun 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-author-response Issues or PRs waiting for more information from the author pr/bug-fix PRs that are specifically addressing a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants