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

Use separate json for each widget #567

Closed
1 of 3 tasks
baev opened this issue Aug 18, 2017 · 0 comments
Closed
1 of 3 tasks

Use separate json for each widget #567

baev opened this issue Aug 18, 2017 · 0 comments
Assignees
@vbragin
Labels
theme:plugin api type:improvement Change that improves some user experience but can't be considered as a new feature

Comments

@baev
Copy link
Member

baev commented Aug 18, 2017

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the motivation / use case for changing the behavior?

Currently all the widgets should be stored in single json file (see widgets.json, graph.json). It would be nice to have separate json for every widget. In that case we can reuse widgets on different tabs.

Please tell us about your environment:

Allure version any
Test framework any
Allure adaptor any
Generate report using any

Other information

Also this change is required for #566
@baev baev added theme:plugin api type:improvement Change that improves some user experience but can't be considered as a new feature work:backlog labels Aug 18, 2017
@vbragin vbragin self-assigned this Oct 23, 2017
@baev baev closed this as completed in 294246f Oct 30, 2017
@baev baev removed the work:review label Oct 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vbragin vbragin

Labels
theme:plugin api type:improvement Change that improves some user experience but can't be considered as a new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@baev @vbragin