CLI reply missing source attributions #24
Comments
|
Oh! I get it. It's not actually a CLI issue, but formatting the response in stream. |
Caulm
changed the title
Caulm
added a commit
to Caulm/BingChat
that referenced
this issue
Jun 13, 2023
[bsdayo#24] Extract the logic of the building answer string. Support formating multiple response messages (containing adaptive cards and source attributions) in both `AskAsync` and `StreamAsync`.
Caulm
added a commit
to Caulm/BingChat
that referenced
this issue
Jun 13, 2023
[bsdayo#24] Extract the logic of the building answer string. Support formating multiple response messages (containing adaptive cards and source attributions) in both `AskAsync` and `StreamAsync`.
Caulm
added a commit
to Caulm/BingChat
that referenced
this issue
Jun 13, 2023
[bsdayo#24] Extract the logic of the building answer string. Support formating multiple response messages (containing adaptive cards and source attributions) in both `AskAsync` and `StreamAsync`.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I noticed that the CLI reply containes citation numbers, like "[^1^]", but does not contain the source attribution link. It looks a bit strange. I'm not sure if this is intentional.
Does it need an option to control whether citations are displayed or hidden?- displayed: For users who want to read the source page for detailed information.- hidden: For users who want to chat or get direct answers.The text was updated successfully, but these errors were encountered: