-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unsetting AllowInvalidUtf8 does nothing #2623
Unsetting AllowInvalidUtf8 does nothing #2623
Conversation
I don't know that I have understood the issue correctly or not, but if yes, I guess I should update CHANGELOG right? |
@@ -80,8 +80,6 @@ impl_settings! { AppSettings, AppFlags, | |||
=> Flags::ARGS_NEGATE_SCS, | |||
AllowExternalSubcommands("allowexternalsubcommands") | |||
=> Flags::ALLOW_UNK_SC, | |||
AllowInvalidUtf8("allowinvalidutf8") | |||
=> Flags::UTF8_NONE, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UTF8_NONE would also need to go
Yes, when this was originally changed, the CHANGELOG wasn't updated, so we need to make sure that happens |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What Ed said.
@epage did I update changelog correctly? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but @pksunkara's word is the one that matters
I think |
Could you clarify how #269 is relevant? The transition from AllowInvalidUtf8 to StrictUtf8 was something kbknapp started in v3, after that issue was closed out. Granted, my proposal in #751 completely changes all of this (switches from |
I remember something about that, but couldn't find anything yesterday while searching. Can you please point me to that? |
I can't find it either. I think my impression came from a misreading of #751 and mixing up spelunking sessions. Interesting enough, it looks like What we need is a determination on #751 so we can know how any of these flags should behave and where. |
That sounds about right. |
so do I need to change anything? |
#2623 (comment) needs to be done as decided in #751 |
@hosseind88 do you want to carry forward with that work? Just want to coordinate so we don't |
@epage you mean that you do it? sorry I have been very busy lately and if you can do it, it would be good |
@hosseind88 alright, I've gotten started on it. |
Closing in favor of #2677 |
Closes #2613