-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
0.60 release checklist #4356
Comments
I would add a check for python's virtualenv |
Latest list of missing commands 1/12/2022
|
TIL zip is already ported |
|
Also add that Work-around:
|
I'm not sure I can do, but I want to try to learn more with just port a simple command , like du ? |
go for it. just copy it from nushell and try to change the primitive types to engine-q types. This issue has some tips at the bottom. nushell/engine-q#242 |
@fdncred did you add my name to the du command already, could you remove for now, seems lot of thing need to learn about nushell and rust . |
sure. no worries. |
Is |
@lukexor Yes, we're leaving autoenv out for the 0.60 release and will re-introduce it later. BTW, what is your use case for autoenv? Do you use it to define environment variables only? Or do you define also custom commands? |
@kubouch Primarily modifying PATH and env vars like JAVA_HOME. Custom commands aren't a concern and have alternative work arounds. At present my only work around is a custom |
This restores a basic version of the `post` command. Some source types have been omitted from this first take. I copied from `fetch` and from `post`@0.40.0. Part of #4356
What's the status of |
we're looking for someone to port it and integrate that functionality into find. are you interested? |
@fdncred I'm interested in this, but I'm not familiar with Rust and if I were to develop it, it might take longer than expected. BTW, I don't know much about the overall architecture of the new engine. Is there a developer guide for the new engine? I think I've seen it somewhere, but I don't remember now. |
I don't want you to get overloaded. it would be nice to finish the examples first, if you don't mind. If you're not interested in finishing the examples, that's ok too. just let me know. |
@fdncred Sure, I will add examples for |
@jaeheonji i'll delete it when the other issue is up. thank you for helping us! |
@fdncred Cool! thank you 😄 I'll try to create an issue ASAP. |
0.60 has long been released. Can this issue be closed? |
ya, we should probably close it. there are things still not ported but apparently no one really needs that funcitonality. |
(warning: this list may not be complete, and may have items added as we discover them):
Commands
find
)$acc
and$it
instead of putting both inside$it
)save --append
group-by --date
sincegroup-by date
is ambiguous with a "date" as a column name')into cell-path? (jt: is there a use case for this one? I think since e-q allows strings as cell-paths you might not need it?)Features
git
as main use case for initial designuse
will look in these dirs)help commands
) (jt: I think we ended up thinking column names should be snake_case. with that being true, cell paths would also be snake_case)Missing config points - to add or not to add?
skip_welcome_message: bool (jt: we no longer show a welcome message, so this probably isn't needed?)pivot_mode: auto, always, never (jt: because of records, some cases we needed this aren't needed anymore. I don't think we need this?)3rd Party Integrations
We should ensure these are working or pr changes to their repo.
Document as "needs design" post-merge
CI / Repo Root folders
Bugs
use
+ path autocomplete: Path autocompletion does not work withuse
argument #4352Checks
ls
through all the filters commands (see fix to retain ls_colors coloring from ls engine-q#824) (fixed sort-by, find, merge, others?)ls_colors
#4309 - closed by fix: losels_colors
in some filters commands #4525first
losesls_colors
#4306 - closed by fix: losels_colors
in some filters commands #4525ls_colors
in some filters commands #4525ls_colors
in some filters commands #4525(ls | sort-by name)
and other subexpressions lose ls_colors #4501The text was updated successfully, but these errors were encountered: