Repository navigation
generate: say why a package with protocols got no Services or serve - #129
Merged
Merged
Conversation
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
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.
comline generatealready warns when protocols on connections disagree on framing or handshake. This adds a note for the silent case: the package declares protocols, but none is on a connection (for example every protocol is server-provided ondatagram@1), so noServices/serve/connectwere generated. It names the framings and links the docs section (ComlineProject/docs#145). A package with no protocols gets no note.Uses
comline_codegen::connectionsat the pinned generation rev; no pin changes.Tests: a package of server-only
datagram@1protocols prints the note; a package without protocols prints nothing extra.