Closed robertjdominguez closed 10 hours ago
The PR introduces a new MetadataComponent but removes a significant block of concrete examples and explanations. This deletion makes it harder for users to grasp model configurations through an illustrative example. While the component itself might be useful, it is not clear how it will convey complex concepts effectively without a practical demonstration. You should consider reintegrating comprehensive examples alongside the MetadataComponent to maintain a balance between abstraction and practicality.
When viewing the changes within the context of the overall documentation, the removal of detailed examples significantly detracts from the usability of the documentation for users looking to understand key-value pairs of a model from an outcome-oriented perspective. The addition of the MetadataComponent may present information in a modular or automated way but does not replace the tangible learning value offered by concrete examples, which directly inform the users how configurations manifest in real-world scenarios. To ensure that the overall usability of the documentation is not compromised, it's crucial that detailed working examples be either preserved or integrated into the MetadataComponent's output.
@robertjdominguez Thanks for your PR! I've assigned @Rob to review it.
Latest commit: |
4f81d60
|
Status: | ✅ Deploy successful! |
Preview URL: | https://b7a3d47e.v3-docs-eny.pages.dev |
Branch Preview URL: | https://docs-iterate-on-models.v3-docs-eny.pages.dev |
Is the PR number for this one an omen? 😱
Do you want me to do a pass?
I'm going to copy the format for the other ones.
Is the PR number for this one an omen? 😱
Do you want me to do a pass?
I'm going to copy the format for the other ones.
Yes, please 🙏
Description 📝
Iterates on models in supergraph modeling with our new metadata component. This is intended to be a first pass and — after collaboration and refinement — will serve as the template for other metadata objects.
A few notes:
Quick Links 🚀
Models
Assertion Tests 🤖
A user should understand the various key-value pairs of a model from an outcome-oriented perspective.