server settings api

[jasonkuhrt]

Once #133 lands it means that there is less reason for users to manually run start. One reason that will remain however is if they wish to pass custom configuration to the server. e.g.:

app.server.start({ port: '1234' })

We should have a more gradual api that doesn't force the user to take on start just because they want to configure something. e.g.:

app.server.configure({ port: '1234' })

[jasonkuhrt]

Alternate names to configure:

app.server.settings({ port: '1234' })
app.server.addToSettings({ port: '1234' })
app.server.changeSettings({ port: '1234' })
app.server.setSettings({ port: '1234' })
app.server.setConfiguration({ port: '1234' })
app.server.settings.add({ port: '1234' })

---

Stream of consciousness start

Considering we want an additive API (multiple calls valid, merging intuitively), something like addToSettings maybe stands out. It would also align with feedback from @schickling about the context api name:

from:

app.addContext({ ... })

to:

app.addToContext({ ... })

But come to think of it, whereas ANYTHING can be added to context, the api for server is about settings, static and predetermined by the framework (and also maybe plugins, in the future), not just raw data build up like the context api.

So never mind...

Stream of consciousness end

---

More brainstorming

app.server.settings.add({ port: '1234' })
app.server.settings.merge({ port: '1234' })
Object.assign(app.server.settings, {
  // ...
})
app.server.settings.set('port', 1234)
app.server.set('port', 1234)
...

[Weakky]

Server setting API is now handled on settings.change({ server: { ... } }). Should we close? cc @jasonkuhrt