FEATURE: create & modify viewpoints

[perfectstrong]

Content

By using Outliner from #69, this feature allows user to:

• Create a new viewpoint by clicking a button in Portfolio, which then open the viewpoint page in which user is free to name the new viewpoint and create new subtopics as well. Test included.
• Consult and modify topics (editing, dragging & dropping, removing from viewpoint). Test not included yet.

Close #92, #58.

---

Checklist

Please check that your pull request is correct:

• Each commit:
  • corresponds to a contribution that should be notified to users,
  • does not generate new errors or warnings at compile or test time,
  • must be attributed to its real authors (with correct GitHub IDs and correct syntax for multiple authors).
• The title of a commit should:
  • begin with a contribution type
    • FEATURE for a behaviour allowing a user to do something new,
    • FIX for a behaviour which has been changed in order to meet user’s expectations,
    • TEST when it concerns an acceptance test,
    • PROCESS for a change in the way the software is built, tested, deployed,
    • DOC when it concerns only internal documentation (however it is better to combine it with the contribution that required this documentation change),
  • be followed by a colon (:) with one space after and no space before,
  • be followed by a title as short, as user-centered and as explicit as possible
    • If it is a feature, the title must be the user action (beginning with a verb, and please not manage),
    • If it is a fix, the title must describe the intended behavior (with should).
  • ends with a reference to the corresponding ticket with the following syntax:
    • (closes #xx) if xx is a feature ticket (and the commit is a complete implementation),
    • (fixes #xx) if xx is a fix ticket (and the commit is a complete fix),
    • (see #xx) otherwise,
• Each committed line is:
  • useful (it would not work if removed)
    • if it is a comment line, its information could not be conveyed by better variables and function naming, better code structuring, or better commit message,
  • related to this very contribution (feature, fix...),
  • in English (with the exception of Gherkin scenarios in French and resulting steps),
  • without any typo in variable, class or function names,
  • correctly indented (spaces rather than tabs, same number of characters as in the rest of the file).

[benel]

A part of your code seems to be from a third party library (probably React-UI-Tree).
Third party libraries should be referenced in package.json rather than being copy-pasted.

[xuzhengyi1995]

Because the library React-UI-Tree doesn't have the function of delete/edit/add, we have modify the library for support these functions. We are sorry but it's not the original library so we can't reference it directly in package.json.

[benel]

Because the library React-UI-Tree doesn't have the function of delete/edit/add, we have modify the library for support these functions. We are sorry but it's not the original library so we can't reference it directly in package.json.

Then the clean (and legal) way is to fork the library and create your own...

[benel]

Then the clean (and legal) way is to fork the library and create your own..

You can also adapt an existing React.Component through composition (rather than inheritance).

[xuzhengyi1995]

I have created my own library and modified the Outliner.

[benel]

I have created my own library and modified the Outliner.

Great!

Your contribution would be perfect if you could now join both of your commits into a single one (like we did in git-graal tutorial).

Note: If you want to push it in the same pull request, you'll have to force it (with -f).

[xuzhengyi1995]

Is join both of the commits like this, thank you.

[benel]

Is join both of the commits like this, thank you.

I'm on it. Thanks.

[benel]

Your contributions are now in branch v7. Well done!

[xuzhengyi1995]

Thank you!