proposal-intl-segmenter
proposal-error-cause
proposal-intl-segmenter | proposal-error-cause | |
---|---|---|
5 | 6 | |
145 | 334 | |
0.7% | - | |
0.0 | 5.7 | |
over 2 years ago | over 2 years ago | |
HTML | HTML | |
- | 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-intl-segmenter
-
String encodings
Splitting by grapheme clusters (or the characters the user actually sees): JS doesn't support this natively, so you'll need a library like grapheme-splitter. There's a Stage-4 proposal in the works, though: Intl.Segmenter:
-
Updates from the 86th meeting of TC39
Intl.Segmenter: Unicode segmentation in JavaScript slides.
-
Is there no .reverse() method for a string like there is for an array?
But even that's not bulletproof. The best method is to divide the string into grapheme clusters before reversing, which is where Intl.Segmenter comes in.
-
The complete guide to working with strings in modern JavaScript
Exactly, and emoji are outside the BMP, so it's not exactly an edge case, but the norm where two code units (UTF-16 double-bytes) are used to make one code point (Unicode character).
And it gets even worse, when you consider that for many purposes you're not even interested in code points but in graphemes -- e.g. a single visible emoji might actually be a combination of 5 code points, represented by 8 UTF-8 code units, taking up 16 bytes.
If you want to split a string by graphemes, you can either use the main dedicated library for it [3], or the relatively new API Intl.Segmenter [4] which is in Chrome and Safari, but still hasn't made it to Firefox [5].
[1] https://blog.jonnew.com/posts/poo-dot-length-equals-two
[2] https://www.contentful.com/blog/2016/12/06/unicode-javascrip...
[3] https://github.com/orling/grapheme-splitter
[4] https://github.com/tc39/proposal-intl-segmenter
[5] https://bugzilla.mozilla.org/show_bug.cgi?id=1423593
-
Emoji under the hood
Also potentially (but not in practice so far) locale-specific. See the FAQ on Javascript's implementation: https://github.com/tc39/proposal-intl-segmenter#why-should-we-pass-a-locale-and-options-bag-for-grapheme-boundaries-isnt-there-just-one-way-to-do-it
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
What are some alternatives?
compressed-emoji-shortcodes - A Quest to Find a Highly Compressed Emoji :shortcode: Lookup Function
proposal-temporal - Provides standard objects and functions for working with dates and times.
grapheme-splitter - A JavaScript library that breaks strings into their individual user-perceived characters.
pony-cause - Ponyfill and helpers for the standardized Error Causes
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
proposals - ✍️ Tracking the status of Babel's implementation of TC39 proposals (may be out of date)
proposal-source-phase-imports - Proposal to enable importing modules at the source phase
types-in-js - Tips and tricks for working with types in JavaScript
zapatos - Zero-abstraction Postgres for TypeScript: a non-ORM database library
proposal-resizablearraybuffer - Proposal for resizable array buffers
proposal-call-this - A proposal for a simple call-this operator in JavaScript.
proposal-string-dedent - TC39 Proposal to remove common leading indentation from multiline template strings