proposal-error-cause
proposal-string-dedent
proposal-error-cause | proposal-string-dedent | |
---|---|---|
6 | 5 | |
334 | 604 | |
- | 0.8% | |
5.7 | 4.1 | |
over 2 years ago | 9 months ago | |
HTML | HTML | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proposal-error-cause
-
GraphQL error handling to the max with Typescript, codegen and fp-ts
:::note When using remote APIs, we often have the possibility to generate the types automatically from a JSON schema for REST APIs, from protobuf files for gRPC-based APIs, from a database schema, etc. You might even be using an external API through an SDK that already provides you with all types. In such cases, the creation of specialized Error classes is not mandatory. However, it might still be a good idea to do so to provide application-specific errors rather than bubbling up 3rd-party low-level errors. For such cases, the upcoming Ecma TC39 proposal for Error Cause is useful as it allows to chain errors. Polyfills exist: Pony Cause or error-cause. :::
-
Updates from the 86th meeting of TC39
Error Cause : .cause property on all Error types slides.
-
Pony Cause 1.0: Error Causes
The impact and cause provides the most value when paired with the other, and that's what Error Cause enables and what Pony Cause is is a ponyfill for and provides helpers for.
-
Error Cause in JavaScript
Well, we have error-cause on stage-3 for the same and with which we could do something like:
-
Updates from the 81st meeting of TC39
Error Cause: Enhancing errors with a distinct "cause".
-
Updates from 78th meeting of TC39
Error Cause
proposal-string-dedent
-
CoffeeScript for TypeScript
We often add promising TC39 proposals into Civet so people can experiment without waiting.
We've added https://github.com/tc39/proposal-pipeline-operator, a variant of https://github.com/tc39/proposal-pattern-matching, a variant of https://github.com/tc39/proposal-string-dedent and others.
Since our goal is to be 99% compatible with ES we'll need to accommodate any proposals that become standard and pick up anything TC39 leaves on the table (rest parameters in any position, etc.)
-
A single developer has been maintaining core.js with little recognition or support. Almost all modern single page apps use core.js. Millions of downloads and hardly any compensation
I was wondering what "dedent" was when I saw this commit since that's what he named the branch. Conveniently, the changelog shows up first in this merge and he Added String.dedent stage 2 proposal which he links. The proposal is a bit dense for me to skim since I'm not particularly familiar with ECMAscript. The code to implement dedent is included and is a bit tricky to skim but if you scroll down to look at what the tests are doing, then the code will hopefully make a bit more sense.
-
Updates from the 90th TC39 meeting
String.dedent: For multi-backtick templates with automatic margin stripping.
-
How to use multi line template literals strings in an IDE while keeping indentation in the IDE (vs code)
There's nothing built in that does this yet, but there is a proposal for a String.dedent that would.
-
Updates from 78th meeting of TC39
String Dedent
What are some alternatives?
proposal-intl-segmenter - Unicode text segmentation for ECMAScript
proposal-source-phase-imports - Proposal to enable importing modules at the source phase
proposal-temporal - Provides standard objects and functions for working with dates and times.
proposal-class-static-block - ECMAScript class static initialization blocks
pony-cause - Ponyfill and helpers for the standardized Error Causes
squint - Light-weight ClojureScript dialect
proposals - ✍️ Tracking the status of Babel's implementation of TC39 proposals (may be out of date)
proposal-intl-locale-info - An API to expose information of locale, such as week data ( first day of a week, weekend start, weekend end), hour cycle, measurement system, commonly used calendar, etc.
types-in-js - Tips and tricks for working with types in JavaScript
proposal-intl-enumeration - Return supported values of options, such as timeZone, calendars, numberingSystems, currencies, units
proposal-resizablearraybuffer - Proposal for resizable array buffers
proposal-json-parse-with-source - Proposal for extending JSON.parse to expose input source text.