Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
This post was edited and submitted for review 1 year ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
In koltin it's common to check the input argument to avoid null value, and I often write a lot of codes like this:
fun test(text: String?) {
text ?: return
// do other things based of text
}
Is this a good coding style? Or there is a better one? Thanks for any comment!
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
For e.g if there is a feature file and if all of the steps are executed successfully then in the report I want to show the status as Pass. I don't want to show the status of each step in the report.
Is there any way to achieve the same
No there isn't. You can ignore the report and use the Results class as described here: https://stackoverflow.com/a/63351980/143475
EDIT: also refer this on how to write custom reports by hand: https://stackoverflow.com/a/66773839/143475
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Do kotlin docs say anything about using the also() function just to reduce code lines? I mean doing some unrelated work in the lambda body and not using the it parameter.
For example instead of this:
fun togglePeriod() {
viewModel.togglePeriod()
showStatistics()
}
I've written this:
fun togglePeriod() = viewModel.togglePeriod().also { showStatistics() }
The code should be readable and express the intention. Reducing the line count for the sake of reducing line count rarely results in the readability improvement.
If toggling a period should result in displaying statistics it makes perfect sense to have a separate togglePeriod() method body, it shows the intention nicely. also() doesn't feel as readable.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I need to notify my team about the approaching code freeze, So what all details should be mentioned in the mail? I want to prepare a standard template.
Thanks in advance
I usually mention the following items:
Code freeze date (date/time of last commit).
Name of the branch that'll be used for the freeze.
Grace period length for critical in-progress issue.
What release/build is this for.
Feature set of such release.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
i am working on some modules,actually change them.
but i don't know how i should document changes in a way that be clear and usefull for future changes.
would someone help me on this issue?
thanks.
If your project is written in one of the languages Doxygen supports, I strongly recommend using that to document your code.
By using Doxygen comments in your source code, you can easily generate documentation in a number of formats by running one command.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
There is so many option in each programming languages which can be mentioned in the code documentation.
I want to know what are the most important Items which we have to document?
I'd document contracts (this parameter is expected not to be null, this function never returns null, ...) as well as the meaning (this method does that, ...). Besides documenting the API, I'd add comments on pieces of code which are non-trivial but add a significant value to the application (cryptic but real fast, works around a framework bug).
What you document ultimately depends a lor on who will read that documentation...