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

Add typed causes for a rejected source and for an opaque argument value

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

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
csharp
Domínio
backend

Direção de pesquisa

Start by reading the parser’s command-name rejection path and the argument analysis types that expose Unknown with ArgKind.DynamicSkip; the issue does not name specific files or tests. Trace how ShellOpaqueCause is currently represented and exposed. Done means parse failures carry a typed reason and argument values expose the three listed opaque causes as public typed facts.

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

Descrição

Problem

Since 0.4.0-beta.18, the parser rejects a source with a brace list in the
command name, such as {"b":2,"nested":{"c":3}}. That is correct, because
Bash expands the word to another program and its operands. But the parser
gives the consumer only an error string. Also, a brace word in an argument
position reaches the consumer as an Unknown value with ArgKind.DynamicSkip,
the same as an arithmetic word or a command substitution. The internal
ShellOpaqueCause is not public.

Netclaw gives the agent a rewrite correction for some unresolved forms. It
needs the cause to choose the correct advice:

  • A rejected source with a brace list in the command name: before beta.18,
    the agent got the "run each command separately" correction. Now 30 corpus
    rows of JSON text get a prompt, or an unattended denial. Netclaw must not
    match the error string.
  • git {push,fetch} origin: Netclaw now gives the general "write the command
    words literally" advice, because it cannot see that the word is a brace list.

Request

  1. Add a typed reason to a parse failure, for example an enum value
    BraceExpansionInCommandName, next to the error text.
  2. Expose the opaque cause of an argument value as a public typed fact, for
    example AnalyzedArgument.OpaqueCauses with the values BraceExpansion,
    ArithmeticExpansion, and CommandSubstitution.

Both facts are general shell syntax facts. They do not depend on a program.

Consumer

netclaw-dev/netclaw#2349, review comment 4187346461.

Linguagem predominante
C#
Estrelas
15
Forks
0
Merge médio
9h 8min
PRs com merge (30d)
46

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 Aaronontheweb/ShellSyntaxTree

Todas as issues de Aaronontheweb/ShellSyntaxTree

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

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