New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add initial implementation #1
Conversation
test/index.js
Outdated
} from 'unist-lsp' | ||
import test from 'tape' | ||
|
||
test('unistPointToLspPosition', async (t) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably good to tests missing props? null/undefined/invalid props?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO it’s fine to rely on type information for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I won’t veto this but generally I believe that it is important to care for users who don’t use TypeScript.
I also believe that, for an open source library, it is important to write “defensively”. As in, assume people pass weird things in, and to an extent, handle that.
People do weird things in plugins. It’s good to not crash on weird things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it depends a bit. I.e. when writing a remark plugin I tend to care about this more then when writing such low-level functions with a specific use cases like these.
Co-authored-by: Titus <tituswormer@gmail.com>
Co-authored-by: Titus <tituswormer@gmail.com>
Co-authored-by: Titus <tituswormer@gmail.com>
Co-authored-by: Titus <tituswormer@gmail.com>
Co-authored-by: Titus <tituswormer@gmail.com>
Co-authored-by: Titus <tituswormer@gmail.com>
Co-authored-by: Titus <tituswormer@gmail.com>
@remcohaszing done? |
Yep, IMO this is good to go. 👍 |
PS I do the following in settings on new repos:
|
Hi! This was closed. Team: If this was merged, please describe when this is likely to be released. Otherwise, please add one of the |
Meh, |
Ready for a release too I presume? |
Annoying!
Yep! Let’s make it version 1.0.0. |
Are you sure it’s wise not to add a |
Also, is |
Bundlephobia is reporting a dep is missing: https://bundlephobia.com/package/unist-lsp@1.0.0. |
I’m not running into any issues anyway.
Oops! #2 |
Initial checklist
Description of changes
This is the initial implementation of
unist-lsp
.