Skip to content

Releases: netcreateorg/netcreate-itest

v1.5.1 January 2024 Data Collection

08 Jan 22:56
@benloh benloh
v1.5.1
5fe333a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.5.1 January 2024 Data Collection Latest
Latest

v1.5.1 for January 11, 2024 Data Collection

  • Numeric input fields default to 0 rather than blank
Assets 2
Loading

v1.5.0 January 2024 Data Collection

23 Dec 21:27
@benloh benloh
v1.5.0
ade7062
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.5.0 January 2024 Data Collection

v1.5.0 for January 11, 2024 Data Collection

Significant Features

v1.5.0 introduces a two new significant features:

  • A new UI for Node and Edge editing that splits out "ATTRIBUTES", "EDGES", and "PROVENANCE" into separate tabs. #39
  • Custom Node and Edge fields can now be added via templates (prior to this you could only rename an existing field). #39

Minor Features

  • A "Focus" filter can highlight a selected node and a customizable range of connected nodes. #275
  • Filters will now show statistics of how many nodes and edges are currently being filtered. #95
  • Filters now support using && and || in search strings. #105
  • Edges now have a weight property that determines the width of the edge. #285
  • Markdown now supports images (with scaling) and emoticons for Nodes, Edges, and tables. #91
  • Research logs now follow a consistent column format so that exports can be more easily compared. #112

Developer Improvements

  • Required node version updated to v18.18.2 (was v18.16.0 and v10.22.0) #89, #2, #1
  • npm version detection now shows errors and instructions for handling Apple Silicon (ARM) processors #1
  • Prettier linting is now fixed and enabled, so code format consistency is maintained. #7
  • Various Visual Studio Code quality of life improvements. #6, #71

And many other infrastructure and minor fixes.

Caveats

  • Template Editor not fully functional -- With the introduction of custom attribute fields, the JSON-Editor functionality is broken. You can still use the Template Editor to change templates for projects that use the default fields, but any project that has custom fields (e.g. fields that have NOT been defined in template-schema.js) will corrupt your template. See #115.
Loading