Title: Define new options api interface and BE-FE options sharing strategy · Issue #142 · sourcejs/Source · GitHub
Open Graph Title: Define new options api interface and BE-FE options sharing strategy · Issue #142 · sourcejs/Source
X Title: Define new options api interface and BE-FE options sharing strategy · Issue #142 · sourcejs/Source
Description: Currently we break up all the settings for back-end modules and front-end modules, which makes configuration a bit more complex, especially with plugins. Proceeding with this structure, users always will need to think about where they sh...
Open Graph Description: Currently we break up all the settings for back-end modules and front-end modules, which makes configuration a bit more complex, especially with plugins. Proceeding with this structure, users alway...
X Description: Currently we break up all the settings for back-end modules and front-end modules, which makes configuration a bit more complex, especially with plugins. Proceeding with this structure, users alway...
Opengraph URL: https://github.com/sourcejs/Source/issues/142
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Define new options api interface and BE-FE options sharing strategy","articleBody":"Currently we break up all the settings for back-end modules and front-end modules, which makes configuration a bit more complex, especially with plugins. Proceeding with this structure, users always will need to think about where they should put config in.\n\nI would like to merge BE and FE options, for easy sharing common parameters. If plugins uses both environments, it could have only one simple configuration:\n\n```\n{\nplugins: {\n plugin: {\n commonOptions: true,\n feOption: false,\n beOptions: false\n }\n }\n}\n```\n\n**The problem:** how to share all the setting with Front-end environment, without exposing private settings, that should not be available externally. Back-end part always have access to everything, for Front-end, only thing that stops us doing the same is privacy.\n\nOne of the solutions is to parse `private` storage, and strip it out on the way to Front-end:\n\n```\n\n{\nplugins: {\n plugin: {\n commonOptions: true,\n feOption: false,\n private: {beOptions: false}\n }\n }\n}\n```\n\nWhere `private: {beOptions: false}` won't be exposed in `/api/options` call from the browser. But it might be not clear for plugin developers, and may cause potential leaks.\n\n**To discuss:** should we expose everything by default, and hide `private` fields, or other way, hiding everything, and showing `common` fields?\n\nAfter defining the solution, we will need to upgrade `/api/options` payload.\n","author":{"url":"https://github.com/robhrt7","@type":"Person","name":"robhrt7"},"datePublished":"2015-05-14T17:35:48Z","url":"https://github.com/sourcejs/Source/issues/142"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:0705dfa9-35e8-1cb5-c8ea-1322e20075f2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E9D8:375283:7CBB77:AF56E4:6AFB6B87 |
| html-safe-nonce | 6e8c4a976815c79a3d6cf064e412941aa7746fa0dcbdbcfba8cc326261f77fd2 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFOUQ4OjM3NTI4Mzo3Q0JCNzc6QUY1NkU0OjZBRkI2Qjg3IiwidmlzaXRvcl9pZCI6IjU3ODkzNTUzMDI0ODIzMDc5NzUiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 4cd9a13da71a1b170c88001ba3a5a50d07fe27bbe15487f62d576084069ec93e |
| hovercard-subject-tag | issue:76432673 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/sourcejs/Source/142/issue_layout |
| twitter:image | https://opengraph.githubassets.com/a121a621d0d557fce7f0d3fad44ab8fce29570ba744266b39e532f5c987f24b5/sourcejs/Source/issues/142 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/a121a621d0d557fce7f0d3fad44ab8fce29570ba744266b39e532f5c987f24b5/sourcejs/Source/issues/142 |
| og:image:alt | Currently we break up all the settings for back-end modules and front-end modules, which makes configuration a bit more complex, especially with plugins. Proceeding with this structure, users alway... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | robhrt7 |
| hostname | github.com |
| expected-hostname | github.com |
| None | cca289ecd54650fcf3c0b037a58b97186dee2cc4406819d87fab93728fd83700 |
| turbo-cache-control | no-preview |
| go-import | github.com/sourcejs/Source git https://github.com/sourcejs/Source.git |
| octolytics-dimension-user_id | 3853046 |
| octolytics-dimension-user_login | sourcejs |
| octolytics-dimension-repository_id | 9578262 |
| octolytics-dimension-repository_nwo | sourcejs/Source |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 9578262 |
| octolytics-dimension-repository_network_root_nwo | sourcejs/Source |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 88808b1fae5ab8a526a73e7ce5542a10eb9d6971 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width