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(schema) more descriptive error logs when type is invalid #6593

Merged
merged 1 commit into from
Mar 18, 2021

Conversation

bungle
Copy link
Member

@bungle bungle commented Nov 20, 2020

Summary

I screwed, sorry @WALL-E, I tried to rebase your original: #6400, but then mistakenly pushes next branch to your next branch, while I was meaning to push the rebased one. Then it closed the PR and I could not push anymore to your branch, Thus here it is again. If this goes green I think we can merge it. Thank you @WALL-E and sorry for inconvenience.

@bungle bungle force-pushed the fix/schema-more-descriptive-error-messages branch 2 times, most recently from fa06a9e to d6e7be5 Compare November 20, 2020 15:19
@bungle
Copy link
Member Author

bungle commented Nov 25, 2020

One thing about this is that should we check if the input is valid utf-8 before concatenating it.

@bungle bungle changed the base branch from next to master March 18, 2021 09:19
@bungle bungle force-pushed the fix/schema-more-descriptive-error-messages branch from d6e7be5 to 2f60c66 Compare March 18, 2021 09:19
@bungle bungle force-pushed the fix/schema-more-descriptive-error-messages branch from 2f60c66 to 965ca1c Compare March 18, 2021 09:35
@bungle bungle merged commit 36c8b2e into master Mar 18, 2021
@bungle bungle deleted the fix/schema-more-descriptive-error-messages branch March 18, 2021 10:14
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.

None yet

2 participants