docs: add conceptual documentation for Stac Registry#473
docs: add conceptual documentation for Stac Registry#473divyanshub024 merged 5 commits intoStacDev:devfrom
Conversation
…ed structure, diagrams, and best practices
|
|
|
@coderabbitai review. |
|
Hey @Shonu72, can you please fix the formatting issue? |
| ```dart | ||
| StacRegistry.instance.register( | ||
| const MyBrandedTextParser(), | ||
| override: true, // This replaces the core "text" parser | ||
| ); |
There was a problem hiding this comment.
StacRegistry.register is declared as a positional optional second parameter, not a named parameter.
There was a problem hiding this comment.
Thanks for the catch! I've updated the sample code in stac_registry.mdx to correctly use a positional parameter for the override flag, matching the actual implementation of StacRegistry.register
The CI failure appears to still be related to formatting differences, even after aligning my local Flutter version with CI (3.41.6), cleaning the workspace, and regenerating dependencies. I’ve ensured that all lockfiles are updated and committed, but the formatting check is still failing in CI. If this continues to be an issue, we might consider excluding example pubspec.lock files from formatting checks or standardizing the Flutter version across contributors to avoid similar CI failures. |
3 participants
Description
This PR adds comprehensive conceptual documentation for the Stac Registry, addressing the lack of clear explanation for this core component.
Key changes include:
docs/concepts/stac_registry.mdxwhich explains what the Registry is, why it's used, and how it manages widget/action parsers and global state.docs/docs.jsonunder the "Concepts" navigation group.Related Issues
Closes #409
Type of Change