Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
My guess would be that it is looking at the code for log4net database appender. Not a lot you can do about this, and unlikely this has changed since even the most recent versions of log4net provide this type of logger. logging.apache.org/log4net/release/…
Sounds like you're consuming from Sitecore directly as a Headless CMS, instead of using the framework. It's possible to support EE in Blazor, but it's not officialy by Sitecore. These might help. youtube.com/watch?v=8whszfkSqrggithub.com/jss-blazor/jss-blazor
Note that JSS Javascript Renderings are deprecated and no longer support since they do not scale well, and it is generally recommended that they are avoided. jss.sitecore.com/docs/techniques/mvc-integration/…
Do you really care about the custom Cache Options showing up in the Rendering Parameters/Control Properties? Is this something that your users are actually using to set cache options? It is much better, centralised and will mean your components being cached as defined by setting this on the Rendering item definition itself.