Repository navigation
docs(v1): explain migration, module filters and internal aliases - #2
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.
Document module-directory-relative paths and per-module module/paths/packages objects in English and Russian. Global filters remain available without listing modules and intersect scoped filters. Explain minimal local migration outputs, optional Go prefix settings, unchanged protobuf import roots, bounded internal aliases and the sole verified materialized snapshot policy.
Validation: MDX generation and TypeScript checks pass. Source examples and behavior are covered by the full v1 suite and real migrated protoc-gen-mcp/service copies. A previous production build attempt was blocked by fonts.gstatic.com; dependencies and application code were not changed for that environment failure.