0.14.0 problem description
See original GitHub issue🐛 Bug Report
Before 0.14.0 when I started a new problem the instructions would be in the new problem file commented out. But now I don’t get the description in the problem’s comments. I just get something like this without the description
/*
* @lc app=leetcode id=35 lang=javascript
*
* [35] Search Insert Position
*/
/**
* @param {number[]} nums
* @param {number} target
* @return {number}
*/
var searchInsert = function(nums, target) {
};
To Reproduce
Start any problem from the sidenav.
Expected behavior
The problems should include the description.
Extension Output
/*
* @lc app=leetcode id=35 lang=javascript
*
* [35] Search Insert Position
*/
/**
* @param {number[]} nums
* @param {number} target
* @return {number}
*/
var searchInsert = function(nums, target) {
};
[35] Search Insert Position
https://leetcode.com/problems/search-insert-position/description/
Tags: algorithms array binary-search
Langs: c cpp csharp golang java javascript kotlin php python python3 ruby rust scala swift
* algorithms
* Easy (40.67%)
* Likes: 1225
* Dislikes: 170
* Total Accepted: 386.1K
* Total Submissions: 948.8K
* Testcase Example: '[1,3,5,6]\n5'
<p>Given a sorted array and a target value, return the index if the target is found. If not, return the index where it would be if it were inserted in order.</p>
<p>You may assume no duplicates in the array.</p>
<p><strong>Example 1:</strong></p>
<pre>
<strong>Input:</strong> [1,3,5,6], 5
<strong>Output:</strong> 2
</pre>
<p><strong>Example 2:</strong></p>
<pre>
<strong>Input:</strong> [1,3,5,6], 2
<strong>Output:</strong> 1
</pre>
<p><strong>Example 3:</strong></p>
<pre>
<strong>Input:</strong> [1,3,5,6], 7
<strong>Output:</strong> 4
</pre>
<p><strong>Example 4:</strong></p>
<pre>
<strong>Input:</strong> [1,3,5,6], 0
<strong>Output:</strong> 0
</pre>
Your Environment
- os: macOS
- extension settings:
{
"leetcode.defaultLanguage": "javascript",
"leetcode.showLocked": true,
"leetcode.enableStatusBar": false,
"leetcode.enableShortcuts": false
}
- nodejs version: 10.15.1
- vscode version: 1.33.1
- extension version: 0.14.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:14 (10 by maintainers)
Top Results From Across the Web
Weird state error with TF 0.14.0 on changes #7945 - GitHub
I think there is an issue with terraform 0.14.0 causing bad state to ... name = "${module.this.id}-https" description = "URL map for load ......
Read more >SpringAdviceTrait (Problem: Spring Web 0.14.0 API) - javadoc.io
Fields inherited from interface org.zalando.problem.spring.web.advice.AdviceTrait ... Modifier and Type, Method and Description.
Read more >Manuskript 0.14.0
A lot of crashes and some potential data loss in the past have been caused by IDs mismatching in the files of a...
Read more >Apache Arrow 0.14.0 Release
The Apache Arrow team is pleased to announce the 0.14.0 release. This covers 3 months of development work and includes 602 resolved issues...
Read more >Solved Problem Definition: 0.12 0.38 0.13 0.37 0.14 0,11
Answer to Solved Problem Definition: 0.12 0.38 0.13 0.37 0.14 0,11. ... This problem has been solved! You'll get a detailed solution from...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I normally have my problems in a repo and in my use case its nice to have the description in the file itself for future reference.
I can see myself going back to the problems a few years from now, maybe outside of vscode, and it would be nice to still have the description easily available.
Having an opt-in option to add the description to the file would be awesome!
I see. Will be back in next version.