Add LQL function bodies and current setting builtin#45
Merged
MelbourneDeveloper merged 1 commit intomainfrom May 6, 2026
Merged
Add LQL function bodies and current setting builtin#45MelbourneDeveloper merged 1 commit intomainfrom
MelbourneDeveloper merged 1 commit intomainfrom
Conversation
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
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.
Summary
bodyLqlsupport for PostgreSQL functions, including YAML validation, DDL generation, and diff idempotencecurrent_setting('key')support in LQL policy predicates and function bodiesValidation
dotnet csharpier check .make lintdotnet test Lql/Nimblesite.Lql.Tests --configuration Release --verbosity minimaldotnet test Migration/Nimblesite.DataProvider.Migration.Tests/Nimblesite.DataProvider.Migration.Tests.csproj --configuration Release --no-build --verbosity minimaldotnet test Migration/Nimblesite.DataProvider.Migration.Tests/Nimblesite.DataProvider.Migration.Tests.csproj --filter "FullyQualifiedName~RlsCurrentSettingLqlTests|FullyQualifiedName~PostgresFunctionBodyLqlTests|FullyQualifiedName~PostgresFunctionBodyLqlE2ETests" --configuration Release --verbosity minimaldotnet test Sync/Nimblesite.Sync.Tests --configuration Release --no-build --verbosity minimaldotnet test Sync/Nimblesite.Sync.SQLite.Tests --configuration Release --no-build --verbosity minimaldotnet test Sync/Nimblesite.Sync.Postgres.Tests --configuration Release --no-build --verbosity minimaldotnet test Sync/Nimblesite.Sync.Integration.Tests --configuration Release --no-build --verbosity minimaldotnet test Sync/Nimblesite.Sync.Http.Tests --configuration Release --no-build --verbosity minimaldotnet test Reporting/Nimblesite.Reporting.Tests --configuration Release --no-build --verbosity minimaldotnet test Lql/Nimblesite.Lql.TypeProvider.FSharp.Tests --configuration Release --no-build --verbosity minimalNotes
make testwas not used for the final pass because theNimblesite.DataProvider.Example.Testsmake target hung in nested build startup locally; the same test project passed when rerun directly with--no-buildearlier in this branch.Reporting.Integration.Testsinitially needed the local Playwright Chromium install; after install, the run hit existing.report-*DOM timeouts unrelated to the LQL/Migration changes and was stopped.