Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Comments on Specify framework / library version in the answer
Parent
Specify framework / library version in the answer
As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from:
As already most of the feedback indicates, the proposed solution seems convoluted and thus hard to implement.
Software Codidact is now small, but as time flows, it will suffer from the same disease: answers are getting older and it would be hard for future readers to understand when a specific answer is correct (minimum and perhaps a maximum version for the framework the answer works for) and when it is not.
Reactions help to deal with outdated answers, but for major frameworks, some answers can be both correct (still work for those using an older version) and wrong at the same time (not working for those using a newer version).
I am wondering about adding a text field next to the answer that allows the answerer to specify the version the answer applies to. That would typically mean the minimum version, but the maximum version can also be specified. Examples for an answer to an Angular question:
>= 4.0.1 and <= 7.1
An even better way would be to clearly separate the minimum version from the maximum one. Both would be optional and free text (to be as simple as possible).
Any thoughts on this proposal? Do you think it would help?
[Edit]
This is a duplicate of this "global" meta post. Unfortunately, closing as duplicate indicating a post from another community is not allowed.
Post
When I first saw this I thought this would be a use case for being able to apply tags to answers (which I've brought up before on Meta, IIRC). But version ranges are a little different, and I don't think you want to necessarily create tags for every version of something just so people can tag answers. (At least we have hierarchical tags, so you could, but it feels like it would often be clutter.)
Code Golf has a similar problem: answers to challenges need to specify the language, and they have a format they expect for answers to accomplish that, and new users have to learn it.
What do you think of the idea of answer labels? I'm thinking of a short textbox, with guidance text that would be configurable per community. Here that text might be something like "applicable version or version range"; on Code Golf it might be "language". Users could type anything; it's not tags. So there could be typos. The label text would be formatted in some way that stands out and would be either embedded in or attached to the answer in some way to be determined.
Would something like this address the issue?
Note: This is just me talking; I don't know what it would take to implement it and haven't asked the dev team about it yet. I'm asking about a potential solution so I know whether to pursue it.
2 comment threads