-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
V6 #216
V6 #216
Conversation
… features stopped being added
The "coverage" script looks to have been replaced previously using jest's configuration. I checked both CI scripts and do not see this being used anywhere
… excess eslint config file note: convert eslint config to js - enables proper comments and variables
…iple Cache types and standardize cacheWrapper calls
I think I solved all open issues including removing the hacky code from @olsonpm can you confirm this is what you had in mind: 60337c9 Questionable commits:
|
i'm not at my computer but the only thing i would add is the file name in the error message similar to how the error is caught and the filename prepended to error message in the loader above |
Good idea. I'll add that tomorrow and hopefully figure out why the windows tests are failing. |
In 358104c I added the file path to the yaml error and fixed the windows errors in db8f2cd. Quick note about the removing Are there any other changes anyone thinks should be done? |
test/caches.test.ts
Outdated
// This test does not work with lazy loading JS -- TODO: fix or remove | ||
// eslint-disable-next-line jest/no-disabled-tests | ||
describe.skip('ensure import-fresh is called when loading a js file', () => { |
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 am unsure how to fix this test. I don't understand the point of the test, don't we know that by requiring it?. I personally think we should just remove it and move on.
@chrisblossom Great work.
I pushed commit ed83eaa with some documentation and changelog adjustments. I think we're ready to launch. Can anybody please chime in if you think we need to wait? If not, I'll merge & publish the release tomorrow (Sunday). |
I can't think of anymore changes and I'm good with merging / releasing.
The |
I released V6 this morning — decided not to spent more time fussing about the lazy requiring, and just see if users have problems with it (the stakes, I think, are pretty low). Nice work! 🍰 🍰 🍰 |
Development of V6 has taken longer than expected, so I've opened the branch
v6
for that work and reverted master to 5.2.1 to avoid confusion.We'll merge v6 work into this branch, then merge it into master when it's ready for release.