Add documentation

[jongpie]

No description provided.

[PawelWozniak]

Could you please add short documentation about the advantages and disadvantages of installing a namespaced package?
I don't know which I should choose.

[PawelWozniak]

Could you please also describe in the documentation if we already have Nebula Logger installed (from the unlocked package) do we have access to this cache manager too?

[jongpie]

Hi @PawelWozniak I'll be sure to address those topics in the documentation. For now, here are some answers to your questions:

Could you please add short documentation about the advantages and disadvantages of installing a namespaced package?

For this package, I don't think there is any difference in functionality - I think the deciding factor is simply if you want/need to use a namespace to avoid issues with existing metadata in your org.

• For example, if you already have an Apex class named CacheManager in your org, you would have issues installing the package without a namespace.
• Some people prefer to use a namespace whenever possible - for myself, I prefer to not use namespaced packages, but in this case, it's just a personal preference.

If we already have Nebula Logger installed (from the unlocked package) do we have access to this cache manager too?

Right now, Nebula Logger and Nebula Cache Manager are independent - Nebula Logger internally uses a LoggerCache class. This class was the foundation & inspiration for Nebula Cache Manager, but they currently are separate, and LoggerCache is really intended to just be used internally by Nebula Logger. So, if you want to use a caching system in Apex, I'd recommend that you install Nebula Cache Manager (instead of using Nebula Logger's LoggerCache class)