Open ghost opened 1 year ago
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
@andreamah @alexdima I don't get why this is put in the backlog, this is not a feature request but a bug 😔 .
This is a feature request because the command is doing exactly what it advertises. The command is called "Transform to Title Case ". It takes text in the form: "SoMe teXT" and will transform each letter after each space to uppercase e.g. "Some Text". The command is not "Transform Camel Case to Title Case" so it doesn't parse the input string as CamelCase and then split it into words.
This is a feature request because the command is doing exactly what it advertises. The command is called "Transform to Title Case ". It takes text in the form: "SoMe teXT" and will transform each letter after each space to uppercase e.g. "Some Text". The command is not "Transform Camel Case to Title Case" so it doesn't parse the input string as CamelCase and then split it into words.
Understood, thanks
:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
Text is not formated in Title Case (transformed to Srecparserloadfromfile instead of Srec_Parser_Load_From_File)
I would expect that SrecParserLoadFromFile
transformed to title case should remain unchanged. The current behavior (transforming into Parserloadfromfile
) might not be what we want, but the proposed behavior (transforming into Srec_Parser_Load_From_File
) is much worse. As @alexdima has properly said, the current implementation is playing it very simple - make the first letter of each word upper, make the rest of the letters lower. Why would you want underscores to appear out of nowhere?..
The feature request here, as I see it, is to alter our understanding of the term word
and treat capital letters inside a sequence of letters as beginnings of new words. This sounds like a reasonable feature request to me
Another option would be to introduce a new command - Transform to CamelCase
for that purpose. But I'm not sure it is worth it.
I would agree that the feature request could be to change the understanding of the word
term.
For the record, the change-case extension does this brilliantly. I consider it such a fundamentally core editing feature that it really ought to be built into VS Code for everyone to use out of the box. (Especially for users who might be using VS Code in other contexts, like Monaco editors on various web pages, who can't install extensions.)
Type: Bug
1- Create a new file 2- Happen the following string
SrecParserLoadFromFile
3- Run the command "Transform to Title Case" (@command:editor.action.transformToTitlecase
) 4- Text is not formated in Title Case (transformed toSrecparserloadfromfile
instead ofSrec_Parser_Load_From_File
)VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:47:18.476Z) OS version: Linux x64 6.0.12-arch1-1 Modes: Sandboxed: No Remote OS version: Linux x64 6.0.12-arch1-1
System Info
|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 2718)| |GPU Status|2d_canvas: enabledcanvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|2, 3, 2| |Memory (System)|23.17GB (13.73GB free)| |Process Argv|--unity-launch --crash-reporter-id 2fff6df5-0f2f-417c-9cf2-2d8bc08e2284| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|plasma| |XDG_CURRENT_DESKTOP|KDE| |XDG_SESSION_DESKTOP|KDE| |XDG_SESSION_TYPE|x11| |Item|Value| |---|---| |Remote|Dev Container: Ubuntu| |OS|Linux x64 6.0.12-arch1-1| |CPUs|Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 2566)| |Memory (System)|23.17GB (13.73GB free)| |VM|0%|
Extensions (21)
Extension|Author (truncated)|Version ---|---|--- language-x86-64-assembly|13x|3.0.0 mermaid-markdown-syntax-highlighting|bpr|1.5.0 jupyter-keymap|ms-|1.0.0 remote-containers|ms-|0.267.0 remote-ssh|ms-|0.94.0 remote-ssh-edit|ms-|0.84.0 remote-wsl|ms-|0.72.0 vscode-remote-extensionpack|ms-|0.23.0 atom-keybindings|ms-|3.0.9 remote-explorer|ms-|0.0.3 material-icon-theme|PKi|4.22.0 devicetree|plo|0.1.1 material-theme|zhu|3.15.6 linkerscript|Zix|1.0.2 doxdocgen|csc|1.4.0 gitlens|eam|13.1.1 gitlab-workflow|Git|3.57.2 cmake-language-support-vscode|jos|0.0.7 git-graph|mhu|1.30.0 vscode-dotnet-runtime|ms-|1.6.0 cpptools|ms-|1.13.7 (1 theme extensions excluded)A/B Experiments
``` vsliv368cf:30146710 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vstes627:30244334 vslsvsres303:30308271 pythonvspyl392:30443607 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 vscorecescf:30445987 pythondataviewer:30285071 vscod805:30301674 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 cmake_vspar411:30581797 vsaa593:30376534 pythonvs932:30410667 cppdebug:30492333 vsclangdf:30486550 c4g48928:30535728 dsvsc012cf:30540253 azure-dev_surveyone:30548225 pyindex848:30577860 nodejswelcome1cf:30587006 3biah626:30602489 gswce1:30612156 iaj6b796:30613358 dbltrim-noruby:30604474 f6dab269:30613381 fim-prod:30623723 ```