2 ms·
> it was in their docs. So not blaming them. We glossed over it. You should be blaming them. You can't excuse dangerous behaviour by documenting it. I feel lik
by IshKebab 2y ago
> it was in their docs. So not blaming them. We glossed over it.
You should be blaming them. You can't excuse dangerous behaviour by documenting it. I feel like this lesson should be known by now.
- suzzer99 2y agoIf the panel setting was specifically for API keys, then yes, that's on apostrophecms. If it's just some kind of generic settings with name/value pairs, then it might make sense to expose those to the browser, and make that very clear up front.
- wouldbecouldbe 2y agoYeah you can define extra global settings extending the existing fields, so we used that for our multi tenancy solution. And is available on the node side of things as well as on the frontend.
- spookie 2y agoWe always need to do our due diligence when using someone else's project. It's an open source project, available for free. If they weren't very clear in the docs is one thing, but it doesn't appear so. Anyway, we won't combat these types of shenanigans by assuming others did everything up to snuff. We gotta be more careful ourselves.