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

[$300 in SQT] Dynamic Datasources destructor #2099

Open
stwiname opened this issue Oct 15, 2023 · 0 comments
Open

[$300 in SQT] Dynamic Datasources destructor #2099

stwiname opened this issue Oct 15, 2023 · 0 comments
Labels
good first issue Good for newcomers guild Tasks that are available via the guild

Comments

@stwiname
Copy link
Collaborator

stwiname commented Oct 15, 2023

Now that we have support for Datasource EndBlocks it should be possible for dynamic datasources to remove themselves and set an end blocks.

From within a handler we can inject a function to destroy the current datasource and it should succeed if it is a dynamic datasource.

This would just be an optimisation to simplify dictionary queries and filtering of blocks

Requirements

  • 80% test coverage on new code
  • Documentation with how to use the feature
  • Codegen to generate a named destructor function
  • A working example project
@stwiname stwiname changed the title Dynamic Datasources destructor [$300 in SQT] Dynamic Datasources destructor Jun 3, 2024
@stwiname stwiname added good first issue Good for newcomers guild Tasks that are available via the guild labels Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers guild Tasks that are available via the guild
Projects
Status: Open Tasks!
Development

No branches or pull requests

1 participant