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
I wanted to bring up an issue with the FileType API. Despite its name and documentation suggesting it supports file handling, the implementation is currently just an alias for StringType and doesn’t handle completions for actual files.
This behavior can be confusing, especially for newcomers, given the conflicting documentation references. For example, the doc comment on the FileType class currently states that it deals with integers, which appears to be a copy-paste error and only adds to the confusion.
I’m also curious whether file completions, if implemented, are intended to be relative to the command’s working directory.
I’m currently working on a project that needs this feature and have already started prototyping an implementation. If there’s interest, I’d be happy to polish it further with unit tests and submit a PR for review.
Thanks for your time!
The text was updated successfully, but these errors were encountered:
Hi,
I wanted to bring up an issue with the FileType API. Despite its name and documentation suggesting it supports file handling, the implementation is currently just an alias for StringType and doesn’t handle completions for actual files.
This behavior can be confusing, especially for newcomers, given the conflicting documentation references. For example, the doc comment on the FileType class currently states that it deals with integers, which appears to be a copy-paste error and only adds to the confusion.
I’m also curious whether file completions, if implemented, are intended to be relative to the command’s working directory.
I’m currently working on a project that needs this feature and have already started prototyping an implementation. If there’s interest, I’d be happy to polish it further with unit tests and submit a PR for review.
Thanks for your time!
The text was updated successfully, but these errors were encountered: