You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is directly false as it's more of a guide on how to use some (not all) shells on some (not all) operating systems. For you to state that the software supports wildcards, the process that is your software must be able to take in wildcards (the process that is your software will only take in a set of relative paths without wildcards by following the implicit intent of the documentation).
To Reproduce
Follow the docs.
System info
You could merge #528 - there was a PR back in 2019 which seems to have been forgotten. Note: I haven't reviewed the code of the PR.
(Yes, yes, yes! But this is a nitpick only! — No, it's actually not; I'm running my commands via Taskfiles that don't support wildcard expansion (quite sanely) — the expectation is that I can type the exact program inputs without knowing the escape rules for my particular shell when codifying commands)
The text was updated successfully, but these errors were encountered:
haf
added
the
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
label
Mar 20, 2024
Describe the bug
According to the docs, I can feed
intl_translation:extract_to_arb
a wildcard path:https://pub.dev/packages/intl_translation#extracting-and-using-translated-messages
This is directly false as it's more of a guide on how to use some (not all) shells on some (not all) operating systems. For you to state that the software supports wildcards, the process that is your software must be able to take in wildcards (the process that is your software will only take in a set of relative paths without wildcards by following the implicit intent of the documentation).
To Reproduce
Follow the docs.
System info
You could merge #528 - there was a PR back in 2019 which seems to have been forgotten. Note: I haven't reviewed the code of the PR.
(Yes, yes, yes! But this is a nitpick only! — No, it's actually not; I'm running my commands via Taskfiles that don't support wildcard expansion (quite sanely) — the expectation is that I can type the exact program inputs without knowing the escape rules for my particular shell when codifying commands)
The text was updated successfully, but these errors were encountered: