Component proper setter/getter, constructor may set its author, normalize optional version - #247
Conversation
7a69ccd to
4a9efaa
Compare
|
I think code should follow existing pattern, so: And the expectation is that Having said that, though, your code change would also be correct, but wouldn't it be better to use the "private" _author field? |
|
re #247 (comment) WHY on earth would one use the internal properties that are not type safe at all, if there are proper setters with type checks? no, in don't think i will use the internal properties. i'll use the existing setters. but i might use the optional-property style you suggested, @shiraze . thanks for the hint 👍 |
shiraze
left a comment
There was a problem hiding this comment.
As discussed in conversation set using optional property style, and we're all good :)
670f7f4 to
73e7c61
Compare
|
na, cannot use shorthand ala |
21b5f45 to
986b85b
Compare
authorauthor, defaults version
1bf0c88 to
3cc38d0
Compare
author, defaults versionauthor, normalize optional version
3cc38d0 to
e47d7e7
Compare
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
e47d7e7 to
5603c70
Compare
148f9f4 to
faf5366
Compare
faf5366 to
d07b8e3
Compare
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
d07b8e3 to
fe6ccfd
Compare
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
author, normalize optional versionComponent proper setter/getter, constructor may set its author, normalize optional version
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
|
@brent-spiner made my day |
component.authornode in generated SBOM #246component.versionvalue #248##233Componentuses setters, so that type-checks are done as expected.##233