Run Flow as an ESLint plugin
The money maker machine.
Compile a JSON.stringify() function with type hints for maximum performance
SE 350 group project for making an OS Kernel
Medley plugin for automatic ETag generation & conditional GET responses
Medley plugin that augments an app to be able to make HTTP requests to itself for testing purposes
The fastest JSON Schema Validator. Supports draft-04/06/07
API Documentation for Firebolt
A simple Battlesnake AI written in NodeJS
Hi @hdehal! I'm glad you think the tool is awesome 😄. Unfortunately it is only designed to convert files in one direction, so it can't convert VTT files to SRT.
comment created time in 3 days
@StingyJack Semantics ¯\_(ツ)_/¯
While uppercase headers can be used at the application level, they will always be sent as lowercase.
However, header field names MUST be converted to lowercase prior to their encoding in HTTP/2. A request or response containing uppercase header field names MUST be treated as malformed (Section 22.214.171.124).
comment created time in a month
Being able to set defaults sounds useful enough that I'd accept a PR that adds the
default property. Alternatively, you could try running the data through Ajv before using this library for serialization. That should work since the schema format that this library uses should be the same as Ajv, and I wouldn't expect Ajv to add much overhead.
comment created time in 2 months
Hi @dalisoft, I'm glad you're finding the module useful. The
default option simply isn't implemented. If you wanted to you could try implementing it, but adding that feature comes with some hard decisions. If the
default option were implemented, either:
- It wouldn't work with the
compileJsonStringifywould have to do a bunch of extra work merging in the default properties when the
true, which doesn't really fit in with the purpose of this module. That additional work might also be slower than setting the defaults yourself before using
compileJsonStringifyto stringify the object.
comment created time in 3 months