Closed Chriscbr closed 1 month ago
Thanks for opening this pull request! :tada: Please consult the contributing guidelines for details on how to contribute to this project. If you need any assistance, don't hesitate to ping the relevant owner over Discord.
Topic | Owner |
---|---|
Wing SDK and standard library | @chriscbr |
Wing Console | @skyrpex |
Wing compiler and language design | @chriscbr |
VSCode extension and language server | @chriscbr |
Wing CLI | @chriscbr |
Documentation | @boyney123 |
Examples | @boyney123 |
Wing Playground | @skyrpex |
Working on adding docs...
Console preview environment is available at https://wing-console-pr-7123.fly.dev :rocket:
I would keep it simple and basically just hoist all interaction panes of children onto their parents without much configuration.
Maybe only hoisting the interaction panes of children that aren't hidden? I think it's important we have some way for an application or library author to choose whether to "reveal" internal details like if they contain Redis caches or DynamoDB tables or S3 buckets inside.
I think I like your idea, simply hoisting stuff everything feels like a sane default
Hi,
This PR has not seen activity in 20 days. Therefore, we are marking the PR as stale for now. It will be closed after 7 days. If you need help with the PR, do not hesitate to reach out in the winglang community Discord. Feel free to re-open this PR when it is still relevant and ready to be worked on again. Thanks!
Closes #7110
As a proposed solution to #7110, this change makes it possible for a parent resource to inherit the UI of one of its children. A child can be configured as the "default" by giving it the ID of "Default" or "Resource"...
... or by explicitly setting setting the
defaultChild
on the resource's internalNode
:Checklist
pr/e2e-full
label if this feature requires end-to-end testingBy submitting this pull request, I confirm that my contribution is made under the terms of the Wing Cloud Contribution License.