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.

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

Implement a "blame" workflow #31

Open
jeffmcaffer opened this issue Jan 21, 2018 · 1 comment
Open

Implement a "blame" workflow #31

jeffmcaffer opened this issue Jan 21, 2018 · 1 comment

Comments

@jeffmcaffer
Copy link
Member

users looking at a summary should be able to tell how an individual value came to be there. Was it harvested by ScanCode? entered by a human (who contributed, who reviewed, who merged)...

Most of the raw information is there today but needs to be collected and presented together in one place. For example, all of the raw data is retained, and the summarizations for each raw tool is available. Similarly, the curations are all PRs with Git commmits, GitHub comments etc.

All the heavy lifting should be done in the service but the UI needs a way to show the outcome.

jeffmcaffer pushed a commit that referenced this issue Sep 28, 2018
)

* increase Section column size

* Added revert function in utils/definition

* Revert All the definitions in Components List

* Revert all changes for an individual definition

* Revert all changes from FullDetailsView

* Updated revert method using action dispatchers

* Adding disabled property to Revert button on definition list elements

* Added Tooltip on PageDefinition buttons

* Added revert icon on InlineEditor

* Added ability to revert any single change in InlineEditor, when used in FullDetailsView

* Revert specific change of a Component on Definition List

* Added ability to Revert FileList Changes

* Fix GlobPicker ref

* Reset preview if there aren't changes

* Added ability to Revert Globs

* Disable Revert Button in FileList

* Removed runtime warnings
@storrisi
Copy link
Contributor

The requirement is to show details about harvesting, curations, and specifically how each data has been found.
This is not completely done in the UI, but there are already some implementations in place, like showing the details of each curation using the ?expanded=prs value, which should return all the details about the pending or merged contributions for the definition, but the service side doesn't answer yet with the expected informations.

@storrisi storrisi added this to the March 2019 milestone Feb 28, 2019
@storrisi storrisi modified the milestones: March 2019, April 2019 Apr 1, 2019
@storrisi storrisi modified the milestones: April 2019, May 2019 May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants