trill | type safe , compiled language | Functional Programming library

Since you are passing an object as data, I strongly assume that axios uses JSON.stringify() to convert that object into a string. The correct JSON representation of the object { value: 'foo\\,bar' } is {"value":"foo\\,bar"}, so with the double quotes and the double backslash.

Now I'm not familiar with axios and its documentation doesn't seem to be very detailed, but maybe try passing a string as data. Then you have full control over the way it is encoded.

A very simple way to try this would be data: JSON.stringify(parsedBody).replace(/\\\\,/g, '\\,').
This will obviously not work if you ever intentionally want to send \\, instead of \,. So depending on what kind of data you are planning to send, you might need to implement your own stringification function (for example: data: `{ value: '${body.value.replace(/([',\\])/g, '\\$1')}' }` )

Try this:

The first option is adding a capitalized name while creating animal object. If that's not possible then you can pass animals list like this

You can use the time class. Depending on how much precision do you need, but you could do:

TypeScript gives you the benefits of static typing only at build time. Your code will be compiled to JavaScript before your application can be executed in the NodeJS environment, so you don't have to worry about returning any strongly typed things, nor about the performance, as there will be no TS at all in your application at runtime.

As for your question about the default value, you can simply check for the value's existence in the map and return a default if there's nothing there.

Either

• use the OS:

  • Windows: How do I view and change the system locale settings to use my language of choice?
  • Unix: How to change locale environment variable?

  OR

• run CLISP with -E UTF-8 command line argument (clisp.exe -E UTF-8 /path/....), OR
• set the default encodings in the init file. Note that setting these variables inside your lisp file which errors out will NOT help because by the time CLISP reads the variables, the file has already been opened in the wrong external format.

This means that you are trying to read (“invalid byte”) or write (“character cannot be represented”) a non-ASCII character from (or to) a character stream which has ASCII :EXTERNAL-FORMAT. The default is described in -Edomain encoding.

This may also be caused by filesystem access. If you have files with names incompatible with your CUSTOM:*PATHNAME-ENCODING*, filesystem access (e.g., DIRECTORY) will SIGNAL this ERROR. You will need to set CUSTOM:*PATHNAME-ENCODING* or pass -Edomain encoding to CLISP. Using a “1:1” encoding, such as CHARSET:ISO-8859-1, should help you avoid this error.

Please see the official site for full documentation.

PS. You now owe me 10 zorkmids

PPS. Your code (list '(...) '(...) ...) looks weird, you might want to replace it with '((...) (...) ...). I mean, your works too, it's just bad style.