Skip to content

fix: do not expose restricted projections #49

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 4 commits into from
Dec 11, 2024
Merged

fix: do not expose restricted projections #49

merged 4 commits into from
Dec 11, 2024

Conversation

torsdag
Copy link
Contributor

@torsdag torsdag commented Sep 13, 2024

Resolves FT-2465912c-2441-11ed-8edb-9e89dc32fb4f

  • I have added automatic tests where applicable.
  • The PR contains a description of what has been changed.
  • The description contains manual test instructions.
  • The PR contains updates to the release notes.
  • I have verified that the documentation is still up to date.

Changes

properties exposed with restricted_projection should not be exposed as attributes.

Test

@torsdag torsdag requested a review from a team as a code owner September 13, 2024 08:41
@torsdag torsdag merged commit b2c1c36 into main Dec 11, 2024
18 of 19 checks passed
@torsdag torsdag deleted the backlog/do-not-expose-restricted-projections-as-properties branch December 11, 2024 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bjornrydahl bjornrydahl bjornrydahl approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@torsdag @bjornrydahl