Add key for privacy_level config attribute#19
Open
tucker-m wants to merge 1 commit into
Open
Conversation
pnpm build @yaltt/backend fails without this, giving an error where it is used in mkYalttToolConfiguration.ts on line 62.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Not sure if this is necessary or if somehow I missed a build step. I'm getting an error when I do
pnpm build @yaltt/backendwithout this. It throws an error in mkYalttToolConfiguration.ts on line 62, saying that this property is not specified.I can make it more specific that just a string if you'd like, I was just trying to get it working again here.