Skip to content

Conversation

@jlian
Copy link
Collaborator

@jlian jlian commented Dec 5, 2025

What changed

  • Restructured WASM samples to match the VS Code extension layout: graphs under wasm, Rust operators under operators, Python operators under operators.
  • Updated builder assets and GitHub Actions to point to new paths; refreshed Rust and Python build instructions and README links.
  • Added schema/state-store scenario placeholders and dataflow graph files alongside operators and sample data.
  • Fixed the WASM development doc copy to align WIT schema links, builder links, example paths, and Python build steps with the new structure.

Testing

  • Docker build: Python map operator from map using python-wasm-builder (produced bin/x86_64/release/map.wasm).
  • Docker build: Rust operator previously validated from an operator directory.

Notes

  • No API/flag changes—only path/layout updates.

jlian added 7 commits December 4, 2025 20:50
…s with appropriate logging and gracefully handle unexpected types
…lper handles Buffer/Bytes; raises on unexpected input to surface an Err, otherwise keeps the threshold filtering logic intact.
…yload to produce an Err; simplified flow while keeping temperature→0, humidity→1 routing.
vipeller and others added 13 commits December 5, 2025 15:22
The Operators source code has been updated to the latest.

## Does this introduce a breaking change?
<!-- Mark one with an "x". -->
```
[ ] Yes
[ x] No
```

## Pull Request Type
What kind of change does this Pull Request introduce?
Changes the operator source in compliant with aziot-operations

<!-- Please check the one that applies to this PR using "x". -->
```
[ ] Bugfix
[ ] Feature
[ x] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:
```

## How to Test
*  Get the code

```
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
```

* Test the code
<!-- Add steps to run the tests suite and/or manually test -->
```
```

## What to Check
Verify that the following are valid
* ...

## Other Information
<!-- Add any other helpful information that may be needed here. -->
## Purpose
<!-- Describe the intention of the changes being proposed. What problem
does it solve or functionality does it add? -->
* ... This PR adds the akri samples needed to test the akri connectors
vscode extension.

## Does this introduce a breaking change?
<!-- Mark one with an "x". -->
```
[ ] Yes
[x] No
```

## Pull Request Type
What kind of change does this Pull Request introduce?
<!-- Please check the one that applies to this PR using "x". -->
```
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:
```

## How to Test
*  Get the code

```
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
```

* Test the code
<!-- Add steps to run the tests suite and/or manually test -->
```
```

## What to Check
Verify that the following are valid
* ...

## Other Information
<!-- Add any other helpful information that may be needed here. -->
…s with appropriate logging and gracefully handle unexpected types
…lper handles Buffer/Bytes; raises on unexpected input to surface an Err, otherwise keeps the threshold filtering logic intact.
…yload to produce an Err; simplified flow while keeping temperature→0, humidity→1 routing.
@jlian jlian merged commit 4a107ee into main Dec 8, 2025
3 checks passed
@jlian jlian deleted the extension-release branch December 8, 2025 20:12
learn-build-service-prod bot pushed a commit to MicrosoftDocs/azure-docs that referenced this pull request Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants