sassoftware / sassoftware/sas-copilot

Generated Code does not include correct dataset name or library

Open
#35 0 comments 0 reactions 1 assignee View on GitHub

@2TomLi is already working on this.

Since Apr 5, 2024.

bug
Dominant language
TypeScript
Stars
12
Forks
1
Avg merge
4m
Merged PRs (30d)
1

Description

Describe the bug
I submitted a prompt to use proc print to output data from work.classes. The generated code shows a different data set name in the case library.

To Reproduce
Steps to reproduce the behavior:

  1. create work.classes dataset (note ! cards data is not lined up properly after the copy/paste from copilot, see attached screenshot):
    data work.classes;
    input lastname $ 1-10 firstnme $ 15-25
    class $ 30-60;
    cards;
    AMMER DAVID English 101
    CANADY FRANK A. World History
    GIBSON MOLLY I. Algebra I
    GIBSON MOLLY I. Creative Writing
    RICHARDSON TRAVIS Z. Enlish Literature
    SMITH KAREN Molecular Biology
    JONES BRENT Biology of Bugs
    WHITMAN REBECCA Biology 101
    BLAKE ANGELA English Grammer
    VOLLER HARRY Overview of Biology
    ;
    run;

  2. submit a request to proc print data from work.classes:
    prompt:
    /* use proc print to show all data in work.classes dataset */
    generated code:
    proc print data=work.class;
    run;

Expected behavior
A clear and concise description of what you expected to happen.

Prompt should generate proc print code for work.classes dataset. Instead it generated code for work.class

Screenshots
If applicable, add screenshots to help explain your problem.

copilot_screenshot.docx

Desktop (please complete the following information):

  • OS: [PC]
  • Version: [v1.8.0]

Reporter's Organization
SAS

Additional context
Add any other context about the problem here.
Initial testing after participating in SAS Viya Copilot Beta testing

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.