Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Web Chat sample names are not informative #1332

Closed
sgellock opened this issue Nov 10, 2018 · 2 comments
Closed

Web Chat sample names are not informative #1332

sgellock opened this issue Nov 10, 2018 · 2 comments
Assignees
@corinagum
Labels
area-docs Documentation required front-burner p1 Painful if we don't fix, won't block releasing
Milestone
v4.2

Comments

@sgellock
Copy link
Member

sgellock commented Nov 10, 2018 •
edited by compulim

When jumping into Web Chat v4, it's difficult to tell (just based on names) what samples to use. Consider summarizing each sample and referencing them from the main Web Chat README.

(Edited by @compulim for branding corrections)
@sgellock sgellock added Approved p1 Painful if we don't fix, won't block releasing area-docs Documentation required labels Nov 10, 2018
@vishwacsena vishwacsena removed their assignment Nov 21, 2018
@compulim compulim changed the title Webchat sample names are not informative Web Chat sample names are not informative Nov 27, 2018
@corinagum corinagum assigned corinagum and unassigned sgellock and compulim Nov 27, 2018
@corinagum
Copy link
Contributor

reference: https://github.com/Microsoft/Botbuilder-samples table

@compulim compulim modified the milestones: v4.4, v4.2 Nov 28, 2018
@corinagum
Copy link
Contributor

corinagum commented Nov 30, 2018 •
edited

* [ ] Create list of which samples still need a README.md
* [ ] Write said README's
* [ ] Comb through samples to link external concepts (such as ponyfilling, redux, etc)
Moved to #1435

@corinagum corinagum mentioned this issue Dec 4, 2018
Merged
@corinagum corinagum mentioned this issue Dec 5, 2018
Closed
23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@corinagum corinagum

Labels
area-docs Documentation required front-burner p1 Painful if we don't fix, won't block releasing
Projects
None yet
Milestone
v4.2
Development

No branches or pull requests
4 participants
@sgellock @compulim @corinagum @vishwacsena