-
Notifications
You must be signed in to change notification settings - Fork 1.8k
C#: Introduce generated flag as a part of the kind column for flow summaries #8628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
1893bec
to
a35b8c7
Compare
a35b8c7
to
387651d
Compare
… particular dataflow callable.
… that will not be discarded at run-time.
…o existing handwritten models.
17a0d1b
to
15061e5
Compare
ce65a48
to
2562910
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
Thoughts on making this its own column? |
We discussed it, but decided to go with this solutions as it is backwards compatible. |
I don't think backwards-compatibility is relevant yet. I think I'm leaning slightly towards making it its own column. @hvitved ? |
I don't really care; I am OK with adding another column for this. |
So should we add an extra column after the kind? |
…mmaries Equivalent of github#8628
…mmaries Equivalent of github#8628
…mmaries Equivalent of github#8628
In this PR, we change the semantics slightly for the "kind" column in flow models.
value
ortaint
) can now be prefixed withgenerated:
.generated
, it is only used in case no summary exist that is not generated.