stub

Is your feature request related to a problem? Please describe.
Today we silently ignore stubbing issues, such as trying to use sinon.stub(obj, 'prop'), when obj.prop is a synthetic getter. From a user perspective, it is probably more user friendly to be explicitly told immediately that this Object.descriptor is non-configurable (perhaps even with a link to a Sinon doc page!) and cannot be

What you did:

Create a route:
/orders/*
then set the delay to 2000ms.

What happened:

route not delayed when hit with another param beside *
/orders/1 not delayed

/orders/900 not delayed
/orders/* delayed
![image](https://user-images.githubusercontent.com/19

Take this class, for example:

`
import Foundation

// some comment has import SOMEBADTHING
public protocol TestProtocol: AnyObject {
func doSomething() -> Void
}
`

The generated mock ends up having:

... import SOMEBADTHING ...

Looks like it is looking for "{import .*}" in source files and just adding that verbatim to the output file, causing compile issues.

Currently, a user can create the mapping to serve the response from random files or in a round-robin fashion. (wiki)

-  request:
      url: /stubs/employee/([0-9]+)

   response:
      strategy: random
      files: ["<% url.1 %>.xml","file2.xml","file3.xml"]

Or

-  request: