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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove def-env and export def-env #10999

Merged
merged 5 commits into from Nov 19, 2023
Merged

Conversation

amtoine
Copy link
Member

@amtoine amtoine commented Nov 8, 2023

follow-up to

Important
wait for between 0.87 and 0.88 to land this

Description

it's time for removal again 馃構
this PR removes def-env and export def-env in favor of def --env

User-Facing Changes

def-env and export def-env will not be found anymore.

Tests + Formatting

After Submitting

- remove the files with
```nushell
ls **/*.rs | find --regex def_env | each { rm --verbose $in.name }`
```
- run `:g/DefEnv/d` in `crates/nu-cmd-lang/src/default_context.rs`
- run `:g/def_env/d` in `crates/nu-cmd-lang/src/core_commands/mod.rs`
@amtoine amtoine added wait-until-after-nushell-release pr:breaking-change This PR implies a change affecting users and has to be noted in the release notes deprecation Related to the deprecation of commands labels Nov 8, 2023
@sholderbach sholderbach added removal-after-deprecation The component has already been sunset with `deprecation` and is now up for final removal and removed deprecation Related to the deprecation of commands labels Nov 8, 2023
@amtoine amtoine marked this pull request as ready for review November 16, 2023 17:46
@WindSoilder
Copy link
Collaborator

Hi @amtoine , would you please fix the conflicts? I believe it's conflict with extern-wrapped changed, because they change the same line..

@amtoine
Copy link
Member Author

amtoine commented Nov 17, 2023

yup, should be better now @WindSoilder 馃槈

@WindSoilder
Copy link
Collaborator

I'm sorry that I didn't review it yesterday, it seems that we still have comflicts...Can you please resolve it again?

this should solve the merge conflict in nushell#10999.
@amtoine
Copy link
Member Author

amtoine commented Nov 19, 2023

no worries @WindSoilder, should be good to go again 馃槈

Copy link
Collaborator

@WindSoilder WindSoilder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure! Let's go, thanks for your work through this

@WindSoilder WindSoilder merged commit 07d7899 into nushell:main Nov 19, 2023
19 checks passed
@amtoine amtoine deleted the remove-def-env branch November 19, 2023 15:27
hardfau1t pushed a commit to hardfau1t/nushell that referenced this pull request Dec 14, 2023
follow-up to
- nushell#10715

> **Important**
> wait for between 0.87 and 0.88 to land this

# Description
it's time for removal again 馃構 
this PR removes `def-env` and `export def-env` in favor of `def --env`

# User-Facing Changes
`def-env` and `export def-env` will not be found anymore.

# Tests + Formatting

# After Submitting
dmatos2012 pushed a commit to dmatos2012/nushell that referenced this pull request Feb 20, 2024
follow-up to
- nushell#10715

> **Important**
> wait for between 0.87 and 0.88 to land this

# Description
it's time for removal again 馃構 
this PR removes `def-env` and `export def-env` in favor of `def --env`

# User-Facing Changes
`def-env` and `export def-env` will not be found anymore.

# Tests + Formatting

# After Submitting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr:breaking-change This PR implies a change affecting users and has to be noted in the release notes removal-after-deprecation The component has already been sunset with `deprecation` and is now up for final removal wait-until-after-nushell-release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants