Repository navigation
Add the Micrate API card for amber-lsp lookup - #97
Merged
Merged
Conversation
shard.lock already records 0.14.0 with its sha256 checksum; the manifest now names the exact version so installs cannot float.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an amber-lsp API card for this library (
.amber-lsp/api/micrate.yml), along with compile probes that check every note against the real API. The card carries:amber-lsp lookupprints next to a method's signature;amber-lsp hintadds to build output;Part of the Amber CLI 2.0.7 lookup work (amberframework/amber_cli#44). This library needs no runtime change: projects that don't use amber-lsp ignore
.amber-lsp/.Also pins
crystal-dbto0.14.0in shard.yml. shard.lock already recorded that version with its sha256 checksum.