whats better server$ api?

server-config-argument.js

const getData = server$((myArg) => {
  console.log(myArg)
});

getData(new ServerConfig({
  method: 'get'
}), myArg)

getData(serverConfig({
  method: 'get'
}), myArg)

server-option-overloading.js

const getData = server$({
  method: 'get'
}, (myArg) => {
  console.log(myArg)
})

getData(myArg)


const getData2 = server$((myArg) => {
  console.log(myArg)
})

getData2(myArg)

server-option.js

const getData = server$((myArg) => {
  console.log(myArg)
}, {
  method: 'get'
})

getData(myArg)

This would be even better:

const getData = server$((myArg) => {
  console.log(myArg)
})
  .method(‘get’);

getData(myArg)

ha thats very JavaScript

I don't want to recreate all the fetch options 😩 also typing that would be insane

3 configs:

• app level: via qwikcity provider in root
• definition level: via object given to server
• call level: via specially tagged first parameter when calling. We already do that for AbortSignal.

I'd prefer having the object first for the definition level, it's easier to read. I don't like chaining.

yeah I can update this in another pr to have 3 levels of configs