-
Notifications
You must be signed in to change notification settings - Fork 11
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
base: main
Are you sure you want to change the base?
Conversation
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'; |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 👌
There was a problem hiding this 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.
Remove deprecated internalize command and its references.
Can we do it?