Open rugk opened 6 years ago
To be more broad and exact we need to drop all template logic, i.e. the template has to deliver all things and only the JS must determinate whether the stuff needs to be shown or not.
Settings, which should still not be exposed via an endpoint:
Is this still an issue or can this be closed?
Ah yeah theoretically for sure, we use server-side-rendering (SSR) here while this issue calls for client-side rendering (which is relatively simple in our case, just fetch the config and hide/show all elements as needed; via JS.). I'll adjust the title, given it is really unclear. The thing I am not that sure anymore is how important it is to achieve https://github.com/PrivateBin/PrivateBin/issues/302 given nearly nobody uses that extension(s), but sure it would be cool to have and a point we could advertise in such a decentralized project.
It would be a benefit without that IMHO though, as the templates may be easier to adjust and less (or even none?) PHP code would be in there then.
Needed for https://github.com/PrivateBin/PrivateBin/issues/302 to make HTML content more static and modify everything only after the settings are loaded/fetched.