Closed aldonline closed 4 years ago
Lol. There are more than 130k valid combinations of settings right now. I need to add some extra restrictions to rule out combinations that don't make sense, like a project with a database and nothing else.
{
fabricui: false,
materialui: false,
spa: false,
spa_webWorker: false,
electron: false,
electron_title: 'My Desktop App',
electron_main: false,
electron_webWorker: false,
lambda: false,
cmd: false,
cmd_pjson_cmd: 'my-cmd',
cmd_pjson_name: 'my-command-cli',
lib: false,
lib_pjson_name: 'lib',
lib_genDocs: false,
cron: false,
cron_expr: 'xx',
ssc: false,
useReactRouter: false,
useReachRouter: false,
orm: false,
orm_forms: false,
orm_crud: false,
cms: false,
mysql: false,
postgresql: false,
docker: false,
netlify: false,
netlify_identity: false,
netlify_triggers: false
},
... 130972 more items
Or... we can differentiate between monotonic settings (that just add, never alter what another setting did) and those that are, effectively, alternatives. I need to untangle the code a bit but that might work.
As we evolve the magic APIs, Magic Create keeps breaking. This happens because the code is generated dynamically (given the options entered by the user), so we don't type check all possible results.
Proposed fix: When compiling the website, we need a way to generate all permutations of possible options automatically and check them with the compiler against the latest types for "@decoupled/magic".