-
Arguments to `next` are parsed like arguments to method calls, but they shouldn't support named parameters:
```cr
next 1, foo: 2
```
This should probably raise a syntax error. Could also captu…
-
If a proxy is configured and the target service is running on a non-default port number (80 for http://, and 443 for https://), the connection always fails because the port number is not passed to the…
-
### Problem
Annotation overrides for StringSlice arguments assume a json encoding instead of using the space delimited behavior used in the arguments and environment variables.
Let's make argument…
-
invariant is using a defined number of arguments `(a,b,c,d,e,f)`
imo it should be
```js
invariant(cond, message, ...args) {
const parsed = message.replace('%s', () => args.shift() || '')
}
```
Sceat updated
4 years ago
-
I have a set of arguments in a specific order. Each needs validation applying to it, so parsing to a method instead of a variable is beneficial. So my code should look something like this:
```
@Argum…
-
### What type of bug is this?
Incorrect result
### What subsystems are affected?
Standalone mode
### Minimal reproduce step
I am encountering an issue when using SQLAlchemy's inspector …
-
**Describe the enhancement:**
https://www.elastic.co/guide/en/security/current/ .html
winlog.event_data.TaskContent XML data is not parsed in elasticsearch:
DOMAIN\user
Deze …
-
``` go
/* how to define go gorilla/rpc func signature if XML-RPC args is comprised as
* 2 arguments: a string argument for actual keyword/method to execute, and
* an array of any XML-RPC type, to be…
daluu updated
7 years ago
-
Hello, Maybe comment on the 54th line "sys.argv = sys.argv[:1]" eval.py, so that the arguments could be parsed successfully. Thanks!
-
### Is there an existing issue or pull request for this?
- [X] I have searched the existing issues and pull requests
### Feature description
When we first wrote Sapphire we added support for `Argum…
favna updated
6 months ago