Adding a protocol for features/cases that aren's supported in a certain target

[tsuf239]

Feature Spec

We should document how we treat cases/features that can be supported in winglang, or are included in the spec but aren't supported in a certain target.

Those cases can be divided into a few:

1. a specific case that isn't supported/ throws an error in one of the targets, and:
   • can be "translated" to fit in the rest of the targets
   • cannot be "translated" to fit into wing
     2. a whole feature that isn't supported in one of the targets.
     3. a feature that isn't supported in wing but in a wide use in the target itself
     4. a feature that isn't supported natively, but a high-cost walkaround exists and so on...

We can collect the answers from the meeting and put them into a new protocol /playbook.

Use Cases

improving our code quality, and less time consumed over decision-making for individual cases.

Implementation Notes

The topic was presented at the Wing Community Meeting (2023-06-20 16:35 GMT+3) (27:00- to the end)

Component

SDK, Documentation

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.

[github-actions[bot]]

Hi,

This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!

[github-actions[bot]]

Hi,

This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!

[github-actions[bot]]

Hi,

This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!