Skip to content

Releases: LabVIEW-Open-Source/URI

1.4.0

30 Dec 22:17
Compare
Choose a tag to compare

[Feature: 11] Support for base paths
[Feature: 9] Map to Local Disk support for absolute and relative paths

Support for UTF-8 URL Encoding

06 Jul 14:01
Compare
Choose a tag to compare

[Feature: 8] Support for UTF-8 URL encoding

Support for Context

17 Jan 02:23
Compare
Choose a tag to compare

Release Notes:
[Fix #6] Fixed the "Construct Path Component" utility VI
[Feature #7] OpenURI now supports "context" (as a String) as well as "port" (as a U16) for better flexibility (feature required to support NI Network Stream protocol)

This Package depends on these other packages:
LabVIEW Open Source Palette >= 1.0.0.2

Features for query and mapping to local path

25 Oct 03:05
Compare
Choose a tag to compare

[Feature: 2] Added a method to append the query elements to an existing attribute variant
[Feature: 3] Adding a method to read a single element from a URI containing a query string
[Feature: 4] Get Path.vi now has an optional flag to strip the leading slash
[Feature: 5] Adding a mapping method to quickly go from URI to Local Path folder

image

Initial release

31 Dec 23:17
Compare
Choose a tag to compare

This is an initial release of the openURI library with basic support for handling RFC3986 Unique Resource Identifiers.
The palette exposes a set of URI composition and decomposition methods that act through regular expressions to manipulate the parts according to the norm.

Official terminology for URIs can be found at https://tools.ietf.org/html/rfc3986

From this example URI:
https://username:[email protected]:443/html/rfc3986?query=test&query2=test2#appendix-A

The library handles decomposition of URI into its basic components:

  • scheme (ex: https)
  • authority (ex: username:[email protected]:443)
  • path (ex: "html/rfc3986")
  • query (ex: "query=test&query2=test2")
  • fragment (ex: "#appendix-A")

Authority is further decomposable into:

  • userinfo (ex: "username:password")
  • host (ex: "tools.ietf.org")
  • port (ex: "443")

Query can further be decomposed into key-value pairs.

Planned future development includes:

  • validation of URIs
  • recognition of URN and URL specificities
  • class-based toolkit with a KVP (key-value pair) dictionary