microsoft / microsoft/vscode-cpptools
Change the settings UI to show the actual default value, instead of empty
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 6.2k
- Fork
- 1.7k
- Merge medio
- 14h 46m
- PR unite (30g)
- 61
Descrizione
@CieroCeramics We thought this issue was a debugger bug, but according to @chrisant996 it sounds like a language service configuration issue that is resolved as @chrisant996 describes. Can we close this issue?
The defines property solved the issue for me. But I'm having to manually clean it up in every project, because each project had UNICODE injected into it. I can sort of understand that approach, except that since defines appeared to be empty I didn't know the UNICODE value was being stamped into every project.
@chrisant996 I don't fully understand what doc change would be best. You could file a doc issue at https://github.com/microsoft/vscode-docs/issues . The default defines are shown at https://code.visualstudio.com/docs/cpp/config-msvc#_cc-configurations .
What could have made things much more straightforward and understandable would have been if the Settings UI showed the actual default value, instead of empty.
- It's non-intuitive that I have to use a different UI than Settings, to change the settings.
- Very early on, I found the C_Cpp.default.defines section. But it was empty. So that makes it looks as though that's not where the "UNICODE" define was coming from.
- Having -- or not having -- a "UNICODE" define is such a fundamental setting for a Windows program that I think it would make sense for the FAQ and core cpptools configuration documentation to specifically use it as an example. Especially since there is a hidden implicit hard-coded default if
definesisn't set in any of the many places it could be set. - Ideally the Settings UI should show the real default value of
defines, instead of empty.
Originally posted by @chrisant996 in https://github.com/microsoft/vscode-cpptools/issues/5244#issuecomment-764445169
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia con la configurazione C_Cpp.default.defines e il comportamento della Settings UI descritto nell’issue, quindi esamina la documentazione collegata sulla configurazione C/C++ per i valori predefiniti documentati. Determina come la UI rappresenta attualmente un valore defines non impostato e verifica che visualizzi il valore predefinito effettivo senza nascondere le sostituzioni a livello di progetto.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- typescript
- Ambito
- devtools, frontend
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100