Standardizing parser/constructor names
See original GitHub issueThe contributing guidelines on safe constructors state:
Prefer
fromString
toparse
.
But in header definitions we consistently use parse
. Should we follow the guidelines or should we change them?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Person Name Standardization and Sun Master Index
The Master Index Standardization Engine can process person data that is provided in separate fields within a single record, meaning that no parsing...
Read more >API:FAQ:Capabilities:Name Standardization
Input Parsing Name Object will parse names into all the individual components. Incoming data can be in varied formats and patterns (Mr John ......
Read more >Name Standardization: Problems and a Solution
It's easy to slice and dice a name by importing NameCleaver and then instantiating a NameCleaver object for a name and calling parse()...
Read more >“gnparser”: a powerful parser for scientific names based on ...
Parsing categorizes name's elements into those that are stable and those that are prone to change. Names are matched first by combining them ......
Read more >HumanName Class Documentation — Nameparser 1.1.2 ...
After parsing the name, these instance attributes are available. Alternatively, you can pass any of the instance attributes to the constructor method and ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s an excellent point. I’m convinced.
I’ve also noticed an ambiguity with the
unsafe
prefix - doesunsafeParse
on an invalid input throw an exception or return an invalid value?HttpCodec
usesparseOrThrow
- I like the clarity but I also like having the prominentunsafe
prefix. How about usingunsafeParseOrThrow
orunsafeParseUnvalidated
to indicate the unhappy-path behaviour?