Skip to content

fix: incorrect isStreamable serialized name #210

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

Merged
merged 2 commits into from
Nov 13, 2024
Merged

Conversation

strantalis
Copy link
Member

The isStreamable was generating the wrong serialized name in the manifest causing json schema validation to fail.

Before IsStreamable
After isStreamable

@strantalis strantalis requested review from a team as code owners November 10, 2024 01:55
Copy link

@strantalis strantalis merged commit 32825b0 into main Nov 13, 2024
7 checks passed
@strantalis strantalis deleted the serialized-name-bug branch November 13, 2024 18:26
mkleene pushed a commit that referenced this pull request Feb 6, 2025
🤖 I have created a release *beep* *boop*
---


<details><summary>0.7.6</summary>

## [0.7.6](v0.7.5...v0.7.6)
(2025-02-06)


### Features

* Add assertion verification
([#216](#216))
([e0f8caf](e0f8caf))
* **cmdline:** assertions cli support
([#204](#204))
([3325114](3325114))
* **sdk:** Add and expose tamper error types
([#187](#187))
([b4f95e6](b4f95e6))
* **sdk:** adds Collections API
([#212](#212))
([1ee1367](1ee1367))


### Bug Fixes

* Correct null assertions when deserializing
([#211](#211))
([b075194](b075194))
* incorrect isStreamable serialized name
([#210](#210))
([32825b0](32825b0))
* NanoTDF secure key from debug logging and iv conflict risk
([#208](#208))
([6301d32](6301d32))
* **sdk:** deserialize object statement values correctly
([#219](#219))
([c513e8c](c513e8c))
* **sdk:** Fuzz testing and protocol fixes
([#214](#214))
([cf6f932](cf6f932))
* **sdk:** group splits with empty/missing split IDs together
([#217](#217))
([0f47702](0f47702))
* **sdk:** remove hex encoding
([#213](#213))
([e076d11](e076d11))
* **sdk:** uses offset for ByteBuffer array offset
([#209](#209))
([0d6e761](0d6e761))
* Use reusable start-additional-kas workflow
([#215](#215))
([cb6f757](cb6f757))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: opentdf-automation[bot] <149537512+opentdf-automation[bot]@users.noreply.github.com>
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.

2 participants