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
Nebulex v3 #149
base: master
Are you sure you want to change the base?
Nebulex v3 #149
Conversation
ea68edb
to
21b071c
Compare
4348690
to
88aa021
Compare
bab2a2d
to
5ffc3ab
Compare
75d8e95
to
dd1fe2a
Compare
1cb7913
to
8430506
Compare
513272a
to
53e570d
Compare
142e5f9
to
01fbeaf
Compare
c6cd5c8
to
82b130a
Compare
f244396
to
71618d5
Compare
@Nezteb thanks!! There are many things to do, a bit of everything 😄 . It could be migrating an adapter to the new API v3 (some planned for the next release candidate), or an essential thing for the first release candidate is reviewing all the guides and fixing them to ensure they are consistent with the new API v3. This will require you to read, understand, and try Nebulex v3 so you can update or fix (or even improve) the guides properly. Let me know if you are interested, we can find something 😉 !! |
e03d047
to
4e4efb1
Compare
6a8369d
to
799cfb9
Compare
64ecfe2
to
a62e2a6
Compare
248790c
to
324b317
Compare
3bf534a
to
0ec9c29
Compare
- Ok/Error tuple Cache API. - Unify `all` and `get_all` into one callback `get_all`. - Remove deprecated module `Nebulex.Hook`. - Use `NimbleOptions` to define and validate cache options. - Move adapters to separate repositories. - All commands optionally support a dynamic cache as the first argument. - Deprecate `Nebulex.Adapter.Stats` in favor of `Nebulex.Adapter.Info`. - Telemetry events for cache commands out-of-box. - Rename the Telemetry metadata field from `:function_name` to `:command`. - Option `:bypass_mode` to skip the cache while running tests - Changes and improvements on Decorator API. - Fix possible inconsistencies on decorators when using references (#215)
No description provided.