Skip to content
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

Fix vector type fields should not be encoded as strings (#2772) #3253

Conversation

bsbodden
Copy link

Pull Request check-list

Please make sure to review and check all of these items:

  • [✅] Do tests and lints pass with this change?
  • [✅] Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
  • [✅] Is the new or changed code fully tested?
  • [✅] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • [✅] Is there an example added to the examples folder (if applicable)?
  • [✅] Was the change added to CHANGES file?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

Addresses #2772

@bsbodden bsbodden force-pushed the bsb/fix-vector-fields-should-not-be-encoded-as-strings-#2772 branch 2 times, most recently from 932de36 to 13105e5 Compare May 29, 2024 03:10
@bsbodden bsbodden force-pushed the bsb/fix-vector-fields-should-not-be-encoded-as-strings-#2772 branch from 13105e5 to 2e28576 Compare May 29, 2024 06:07
@bsbodden bsbodden closed this May 29, 2024
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.

1 participant