forked from almende/vis
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add badge support #11
Open
kinjal-gandhi
wants to merge
406
commits into
master
Choose a base branch
from
badge
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lmende#2729) * Improve the performance of the network layout engine Short-cut the execution of a number of methods in LayoutEngine to make them handle highly-connected graphs better. * Demonstrations of layouts of large networks
Somewhat more complicated setup, associated with the need for a real window.
…lmende#2774) This addresses almende#1982 and almende#1417. It possibly reduces performance, but correctness seems better.
…nde#2760) * Added support to supply an X2 to bar charts to have them scale * Fixed graph2d stacking issue. It no longer takes into account hidden items * Changed x2 to end per recommendation and added this to the docs
* Fix redraw order * Fix error when option is not defined * Allow template labels * Add .travis.yml file * Add experiment travis code * Fix react example * Fix events returned from mouse events * Fix example * Rename censor to stringifyObject in example
* Fix for issue almende#2536 * Adjusted documentation for fix. * Adjustments due to review * Grrrrr whitespace * Fixed Travis issue
…mentation (almende#2802) * Add edited data as argument to the template function * Update index.html
…ation: top` (almende#2831) * Fix background items when orientation top
…ut item overrides. (almende#2806) This is to reduce breakage if the fallback / default changes in a future release.
…e#2540 (almende#2812) * Adjusted doc for autoscaling; ref Issue almende#2540 * Edited Defaults column for Min/Max options for completeness
…port es5+) (almende#2829) * Fix redraw order * Fix error when option is not defined * Allow template labels * Add .travis.yml file * Add experiment travis code * Fix react example * Remove assign from examples * Use jQuery
* Fix redraw order * Fix error when option is not defined * Allow template labels * Add .travis.yml file * Add experiment travis code * Fix react example * Add animation options for zoomIn and zoomOut
* styling support for graph3d tooltips * styling support for graph3d tooltips * graph3d styling example, deleted new example and altered the original * graph3d tooltip styling, documentation * graph3d tooltip styling, use the util module's method for merging objects
Fix proposal for issue almende#2842 More details here : almende#2842
almende#2852) Don't update the showNested property if nothing has been set in the data object, unless it is undefined. Verify group object exists during `onGroupClick`
* Add methods to remove and add items to a subgroup. Add method to change the subgroup an item is in. No longer decrement subgroup ID when removing a subgroup. Fixes almende#2594 * Moved the orderSubgroups call outside of the add/remove methods. Added the ability to call the add/remove methods without a subgroupId parameter (takes from item data instead).
* Initial refactoring * Small refactoring BarnesHutSolver * Disabled debug routine, empty lines removed * Put back space in comment * Typo
Some browsers cannot handle very large DIVs so by default range DIVs can be truncated outside the visible area. This change allows the use of a new `limitSize` item option which disables this functionality, allowing the creation of full-width DIVs. I don’t see an existing test spec that covers RageItem.js so I’m submitting without tests. However we’ve using Timeline in production on a fairly large project with these changes in place for several months and it works fine.
* Cleaned up some whitespace and added test for issue * Checking for proper removal, better comments and whitespace cleanup
* Make items redraws return queues * Parallel initial items redraw * Seperate read and write actions in items * Parallel all items redraws * Remove comments * Fix linting comments * Fix redraws on actions * Seperate group read and write * Add objects that can be dropped to items * Move example * Fix group get/set group properties * Add documentation * Remove console.log * return Group.js changes * Fix review comments * Fix example * Update drag&drop.html
* initial trial * Add onInitialDrawComplete * Add docs * Add to eventListeners examples * Keeping things DRY * Remove callback insertion * Remove call * Fix initial real first draw complete and fix comments from review * remove all <code><code>
* Network: Retain constraint values in label font handling Fixes almende#3517. Due to changed logic in the label font handling, the option values for `widthConstraint` and `heightConstraint` were overwritten. The fix is in effect a reversal of two code lines: parsing constraint options should come *after* parsing (multi)font options. Further changes: - Additional 1-liner fix: constraint values were not copied for edge-instance specific options. - Small refactoriing of `Label#constrain()` in order to separate concerns - Added unit test for regression testing of this issue. This leads to the curious observation that, while the actual change is two lines of source code, this resulted in a +-150 line regression test. * Made unit test more linear, removed tabs * Made 'enhanced subset' of unit test * Removed TODO from comment * Culled redundant nodes from unit test
…s to cluster (almende#3554) Previous condition was too strict: if *any* node for the cluster was already clustered, the clustering would abort. Current fix scans for already clustered nodes and proceeds with what is left.
almende#3626) * Adds code-coverage badge, code coverage reports, and test-cov script to master. * install nyc * Correct badge url
* removed badges from readme * updated history * updated the README * update the github templates * update the github templates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.