Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Don't rely on IDE=VSCode in querystring for behaviour

Aberta
  • Algo errado?
#9,811 9 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Refatoração
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
dart
Domínio
developer-experience, tooling

Direção de pesquisa

Revise o tratamento de IDE em packages/devtools_app/lib/src/shared/development_helpers.dart, packages/devtools_app/lib/src/shared/preferences/preferences.dart e packages/devtools_app/lib/src/standalone_ui/ide_shared/property_editor/property_editor_panel.dart. Primeiro, rastreie como os valores de IDE chegam à string de consulta e teste o comportamento de fallback do WASM. Considera-se concluído quando o filtro da pesquisa, a mensagem de fallback e o link da documentação do editor de propriedades funcionarem corretamente para VS Code, Antigravity, Cursor e outras variantes de IDE.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

devtools-ide-integration ide: vs-code P1

https://github.com/Dart-Code/Dart-Code/issues/5970 is a request to change the values pass in the querystring passed to DevTools to include the proper IDE name and not hard-coded values like "VSCode" (which prevents distinguishing VS Code forks using the same extension, like Antigravity or Cursor).

However, there are some places that currently assume "VSCode" here in DevTools that I think require reviewing first (or, we need to pass two values).

  1. Survey IDE filters
  2. WASM/JS fallback message
  3. Property editor documentation link

1. Survey IDE Filters

https://github.com/flutter/devtools/blob/6046c5bef397cbac6eb9e5d535436ef2b3bb6dbb/packages/devtools_app/lib/src/shared/development_helpers.dart#L229-L231

I don't know if this is used, but if it is, it would need to cover each of the variations of editors now. I think we could either:

  1. Update this comment to mention this is based on DASH__IDE_NAME and include updated examples ("Visual Studio Code", "Antigravity", "Cursor")
  2. Pass two values in querystring, DASH__IDE_NAME and also DASH__TOOL (or DASH__PLUGIN_NAME) which are constant across different IDE flavours using the same plugin/extension

2. WASM/JS fallback message

https://github.com/flutter/devtools/blob/6046c5bef397cbac6eb9e5d535436ef2b3bb6dbb/packages/devtools_app/lib/src/shared/preferences/preferences.dart#L239-L250

It controls whether to show a message if the wasm version fails. I'm not sure if this is necessary anymore, as I think there were WASM changes to not require COI? If so, this code could probably just be deleted (and if not, I think won't cause any problems). Needs testing though.

3. Property editor documentation link

https://github.com/flutter/devtools/blob/6046c5bef397cbac6eb9e5d535436ef2b3bb6dbb/packages/devtools_app/lib/src/standalone_ui/ide_shared/property_editor/property_editor_panel.dart#L172-L179

If IDE is not exactly "VSCode" this will link to the Android Studio docs.

Linguagem predominante
Dart
Estrelas
1.7k
Forks
408
Merge médio
4d 20h
PRs com merge (30d)
11

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de flutter/devtools

Todas as issues de flutter/devtools

Issues semelhantes

Mais issues de Dart

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.