Skip to content
This repository has been archived by the owner on Jul 29, 2019. It is now read-only.

Activating Open Collective #3649

Closed
wants to merge 38 commits into from

Conversation

asood123
Copy link

@asood123 asood123 commented Nov 6, 2017

This pull request adds backers and sponsors from your Open Collective https://opencollective.com/vis ❤️

It adds two badges at the top to show the latest number of backers and sponsors. It also adds placeholders so that the avatar/logo of new backers/sponsors can automatically be shown without having to update your README.md. [more info]. See how it looks on this repo.
We have also added a postinstall script to let people know after npm|yarn install that you are welcoming donations (optional). [More info]
You can also add a "Donate" button to your website and automatically show your backers and sponsors there with our widgets. Have a look here: https://opencollective.com/widgets

P.S: As with any pull request, feel free to comment or suggest changes. The only thing "required" are the placeholders on the README because we believe it's important to acknowledge the people in your community that are contributing (financially or with code!).

Thank you for your great contribution to the open source community. You are awesome! 🙌
And welcome to the open collective community! 😊

Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other open source sustainers!

yotamberk and others added 30 commits October 12, 2017 16:10
Fixes almende#3543.

None of the options passed in any of the API calls should change the options. This has been registered with issue almende#3548.
…ation (almende#3568)

* Network: Prevent crash when dataChanged is triggered during initial setting of options

Fixes almende#3562.

Options `hidden` and `physics` can emit a `_dataChanged` event within `setOptions()`.
If this happens when setting options during the initialization of the `Network` instance, this leads
to an error thrown, because there is no DataSet instance  connected yet to the instance.

This bug was introduced in `v4.21.0`. Unit tests have been added for this case.

* Edited comment
* Use mock canvas object replacing `canvas`

Fixes almende#3515.

A mock canvas object is added to the unit tests, which makes usage of module `canvas` voluntary.

The issue with `canvas` is that it requires an external dependency to `cairo`. This complicates setting up a develop environment for `vis.js`

- Removed `canvas` from `package.json`
- Added section to README.md with instructions on how to install `canvas` instead.

* Removed debugger statements

* Updates for review

* Fixes for review
)

Bumped up the version number in the examples using `FontAwesome`, in order to avoid confusion about missing (new) icons as in almende#3408.
Fixes almende#3532

If the images option is set, preload it, even if the node shape is not `image` or `circularImage`.
This needs to be done because the user can switch to an image shape later, as is happening in the issue.
Option `image` is only mandatory for the image shapes.

There is no unit test for this, because it would need a mock object for Image and I didn't succeed in creating/finding one.
* Network: preload images in options for all shape types

Fixes almende#3532

If the images option is set, preload it, even if the node shape is not `image` or `circularImage`.
This needs to be done because the user can switch to an image shape later, as is happening in the issue.
Option `image` is only mandatory for the image shapes.

There is no unit test for this, because it would need a mock object for Image and I didn't succeed in creating/finding one.

* Network: Handle null data gracefully

During testing I discovered that passing `null` for network data leads to a thrown error.
This adds a guard to prevent it, plus unit tests for regression.
This shape was added recently and was not showcased anywhere. Hereby added.
Fixes almende#3468.

Rather than changing the code, this resolves the issue by adjusting the documentation for event `stabilized`.
* initial trial

* Add onInitialDrawComplete

* Add docs

* Add to eventListeners examples

* Keeping things DRY

* Remove callback insertion

* Remove call

* Add initial loading screen

* Fix real initial draw call

* Remove activateOnInitialDraw method

* Add loading screen option

* Add docs

* Remove onInitialDrawComplete double doc

* Simplify example

* Simplify stressPerformance example

* Remove extra line
almende#3575)

* Adds code coverage report the output of `npm test` and adds detailed html code coverage report using the command `npm run-script test-cov`

* Switch over to using functions in lib/ rather than dist/, so that code coverage stats are complete.

* Import vis at the top level to keep ItemSet passing

* Remove requirement for dist/vis in TimelineItemSet
* Interim save cleanup typedefs

* Completed transferral of *the* big typedef

* Transferred all typedefs to typedefs.js
* Network: DRY code in Label for parsing markup

This gets rid of a major eyesore for me. The accumulator object was identical for HTML and  Markdown.

In addition, the parsing has been refactored. Common elements have been DRY'd and the logic of the parsing has been made more comprehensible.

* Added suggestion @mbroad wrt regexp precompile

* Fixed linting
* Move majorLables to 1st week in the month, for 'week' scale

* next() always adds 1 week to current date
* show 1st week in the month as majorLabel

* Add 'week' to auto-scale

* Update week scale example

* Revert "Move majorLables to 1st week in the month, for 'week' scale"

This reverts commit 52df3c3.

* Correct value of week's minimumStep
* Add template for document generation with 'jsdoc'.

In essence, it defines the subdirectory `docs` as a `jsdoc` template. Benefits:

- allows the usage of partials, in order to DRY common parts of the html files.
- makes available the jsdoc-comments, for addition into the documentation.
- enables extraction of data from the source code. For example, the list of edge endpoints `['arrow', 'bar', 'circle']` can now be extracted from the source and inserted into the documentation on generation.

In this initial version, the only file that has been changed is `docs/data/dataset.html`.
In here, partials have been added to illustrate how common page elements can be DRY'd.

The template has been set up in such a way, that resource files will be copied and that html files can pass through unchanged if no special template tags (`<?js...?>`) are used. This allows for a gradual transition of the html files to templates.

**Usage:**  `gulp docs`

- The result files are placed in subdirectory `gen/docs/`.

**NOTE:** The release procedure will have to be adjusted by adding this gulp command.
The docs-files will then have to be taken from `gen/docs`.

* Edits to docs/README

* Adjusted layout of README.md

* Further edits to README.md

* Removed pre tags again in  README.md - don't work in code block

* Linted the gulpfile

* Added proof of concept for docs generation from source
…3576)

* Network: force array order when sorting hierarchical levels

Fixes #340r34.

If coordinates are not available to sort within a hierarchical level, sort to array order instead.

The previous fix on this issue was not good enough to circumvent this quirk in the chromium sorting. This should bury it.

* Added TimSort for sorting in DirectionStrategy

* Added TimSort to LayoutEngine

* Fixed typo
…mende#3597)

* Added partial, tested with some pages

* Docs: Moved end block in all html documentation files to partiel

This rcConsolidatersd common footer in all documentation files to a partial.

I'm hoping this serves as an example for others to isolate more common blocks (the menu would be the perfect candidate). It's straightforward work.
…ende#3604)

* Moved navbar elements in all html documentation files to partial

This consolidates the common menu elements in all documentation files to a partial.

* Moved test-exclamation mark
* background docs
* edge background
* Update edges.html
* Update EdgeBase.js
…rk (almende#3603)

* First working version

* Fix completed for jsdom getContext() issue

* Fixed commenting for review
…e#3596)

* Docs : fixes and enhancements for the documentation template.

This is an evolutionary update for the `jsdoc` document generation.

- Added functionality to retrieval of data comments
- Added partial for generating documentation in the method tables.
- Moved commenting to source for `Network#clusterOutliers`. This was used as a case example.

- Adjustment to CSS to get the decription text margins same as original
- Added step to generate documentation to release checklist
- Fixed some commenting which `jsdoc` couldn't handle

* Fixes for linting
* Adds code coverage report the output of `npm test` and adds detailed html code coverage report using the command `npm run-script test-cov`

* Switch over to using functions in lib/ rather than dist/, so that code coverage stats are complete.

* Import vis at the top level to keep ItemSet passing

* Remove requirement for dist/vis in TimelineItemSet

* Adds tests for Popup

* Tests and sinon dependency introduced

* Code changes to modules to tighten up code

* Corrects broken tests and adds more tests to ColorPicker

* Adds additional tests to DataSet

* Adds tests for uuid

* Removes unused functions from util

* Adds tests for utils: recursiveDomDelete, isDate, convert and isType

* removes redundant code

* Adds additional util tests

* Address spacing, and unnecessary tests

* Correct test description

* Adds isDate tests

* Adds sanity check assertions to popup destroy tests
…#3633)

* Prevent items from being repeatedly redrawn while off screen

Fixes almende#3249 again, because my previous PR got overwritten

* Add JSDocs for almende#3633
asood123 and others added 5 commits November 6, 2017 13:52
almende#3646)

* Fixes issue 3321 by ensuring labels are drawn as part of initial construction of the DataAxis

* Simplify test and remove support for node 6

* Exclude test coverage from regular test runs
* Fixes issue 2584

* Trims graph manipulation image
…top (almende#3652)

When the mouse was over a group-label's very top pixels, no group id was returned in mouse events.
This was due to checking if the cursor's Y coordinate is higher than the group element's top position, and not equal or higher.
@yotamberk
Copy link
Contributor

Can you resubmit this to the develop branch aswell?

@mojoaxel
Copy link
Member

@asood123 Thanks again!
As @yotamberk mentioned we usually don't change the master branch and do all changes in the develop branch. (This git flow was introduced by almende and we got used to it, sorry).

As mentioned in #3680 I'm going to fix this my cherry-picking your changes and resubmitting them. Thanks again!

@mojoaxel mojoaxel closed this Nov 23, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.