I've been seeing a lot of these questions lately:
- object.Storage.js - creates a namespace for Storageobject.Storage.js - creates a namespace for Storage
- http://codereview.stackexchange.com/q/127923/11919https://codereview.stackexchange.com/q/127923/11919
- http://codereview.stackexchange.com/q/127853/11919https://codereview.stackexchange.com/q/127853/11919
- http://codereview.stackexchange.com/q/125950/11919https://codereview.stackexchange.com/q/125950/11919
- http://codereview.stackexchange.com/q/125828/11919https://codereview.stackexchange.com/q/125828/11919
- http://codereview.stackexchange.com/q/125722/11919https://codereview.stackexchange.com/q/125722/11919
- My favorite privacy settingsMy favorite privacy settings
TL;DR: Should these be closed?
They all refer to this "private" framework called $A whose origins I can't find anywhere. The posts never mention what $A is. The closest I can find is SalesForce Lightning but it doesn't even resemble any of the code.
One of them mentions that it's a private library. What are the chances of $A being a private library when they're asked by different people and written in the same way? Could it possibly come from a some starter kit? If so, can it be dismissed as code not owned/maintained?
The code is also very sparse, not much to go by. Only one of themOnly one of them (the last one) shows that this framework even works, but just a screenshot. The rest are asked in a fire-and-forget manner. And even if it is a private library, there should at least be a primer of what it does in the post. Should these questions be closed for being too broad/unclear/lack of references?
PS: I still doubt it's a private library. It makes no sense asking other people about code that doesn't even exist outside private unless it's very generic that anyone can give recommendations regardless of accompanying private tooling.