Release v0.1.0

[xhluca]

About

Ending project #1

[0.1.0] - 2019-04-05

Added

• Four new demos:
  • demos/usage-dag-edges.py: Show different types of edges in a DAG. It uses the new dash_cytoscape.utils.Tree class.
  • demos/usage-elements-extra.py: Shows how to load external layouts, otherwise same app as usage-elements.py.
  • demos/usage-preset-animation.py: Example of animating nodes using the preset layout.
  • demos/usage-reset-button.py: Example of resetting the graph position using a button.
  • demos/usage-remove-selected-elements.py: Example to show how to remove selected elements with button.
• dash_cytoscape/dash_cytoscape_extra.[min|dev].js: New bundles containing the extra layouts. Those bundles are double in size compared to the default bundles. Therefore, they are only loaded when the user uses load_extra_layouts() to limit bandwidth usage and maximize loading speed. Please view fast3g-cytoscape for an example of the impact on loading time.
• dash_cytoscape._display_default_values(): A util function to display the default prop values by reading metadata.json. Useful for documentation.
• dash_cytoscape.load_extra_layouts(): A new function that can be called before initializing the Dash app (app = dash.Dash(__name__)) to load the JS bundle containing the external layouts.
• src/lib/extra_index.js: Loads external layouts before exporting the Cytoscape class. Needed to generate the new bundles.
• webpack.[dev|prod].extra.config.js: Two new webpack configs for external layouts.
• Images of new external layouts.
• You can now feed a dictionary with keys nodes and edges to the elements prop of Cytoscape, instead of a list. The respective values will be lists of nodes and edges.

Changed

• usage-events.py: Added IDs for the edges in order to pass Percy tests.
• src/lib/components/Cytoscape.react.js: Updated docstring to include information about new external layouts and warning about nodes that can't be modified by a callback. Added more default props for a better expected behavior.
• package.json: Added new builds for the extra layouts, modified npm build:all to include new builds. Added external layouts as dependencies.
• MANIFEST.in: Include new dash_cytoscape.[min|dev].js files.
• README.md: Moved images, added more images at the end, added useful links.

Fixed

• Removing selected elements will now be automatically removed. Fixed by PR #49, fixes issue #45.

Checklists

Beginner tip: Copy and paste this section as a comment in your PR, then check off the boxes as you go!

Pre-Merge checklist

• The project was correctly built with npm run build:all.
• If there was any conflict, it was solved correctly
• All changes were documented in CHANGELOG.md.
• All tests on CircleCI have passed.
• All Percy visual changes have been approved.
• Two people have 💃'd the pull request. You can be one of these people if you are a Dash Cytoscape core contributor.

Merge step

1. Make sure to Squash and Merge your contribution if you have created multiple commits to change a specific feature.
2. Make sure to Rebase and Merge if you added many different features, and need to contribute multiple different commits.

Post-Merge checklist

• You have tagged the release using git tag v<version_number> (for the contributor merging the PR).
• You have pushed this tag using git push <tag_name> (for the contributor merging the PR).
• You have deleted the branch.

Pre-Release checklist

• Everything in the Pre-Merge checklist is completed.
• git remote show origin shows you are in the correct repository.
• git branch shows that you are on the expected branch.
• git status shows that there are no unexpected changes.
• Both package.json and dash_cytoscape/package.json versions have been correctly updated.

Release Step

Complete the "Publishing" section.

Post-Release checklist

• Step 1 and 2 of Post-merge checklist are completed.
• You have closed all issues that this pull request solves, and commented the new version number users should install.
• If significant enough, you have created an issue about documenting the new feature or change and you have added it to the [Documentation] project.
• You have created a pull request in [Dash Docs] with the new release of your feature by editing that project's requirements.txt file and you have assigned @chriddyp to review.

[shammamah-zz]

Cytoscape is getting better and better 💪