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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Breaking Change] Fully abandon the already deprecated internalize 🫂 #75

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

promatik
Copy link
Contributor

Remove deprecated internalize command and its references.

Can we do it?

Comment on lines 7 to 11
case LOADED = 'Already loaded';
case IN_CACHE = 'Already in cache';
case INTERNALIZED = 'Internalized';
case CACHED = 'Cached';
case INVALID = 'Not in a CDN or local filesystem, falling back to provided path';
case DISABLED = 'Development mode active';
Copy link
Member

Choose a reason for hiding this comment

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

Changing the enum is a BREAKING CHANGE. I vaguely remember using this somewhere... In backpack maybe? Idk. But it was like... if the response from basset is IN_CACHE then echo whatever.

If we change the enum... that response will change...

So it's a breaking change.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oooh, that's right 👌
Delaying to next version 👌

Copy link
Member

@tabacitu tabacitu left a comment

Choose a reason for hiding this comment

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

I agree with this. But not now - it's a breaking change.

@promatik promatik changed the title Fully abandon the already deprecated internalize 🫂 [Breaking Change] Fully abandon the already deprecated internalize 🫂 Jul 31, 2023
Base automatically changed from check-command to main August 1, 2023 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

3 participants