Skip to content

feat: exposed metadata storage #996

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

MHekert
Copy link

@MHekert MHekert commented Nov 21, 2021

Description

Exposed metadata storage to allow for manual coping of metadata to derived class.

Checklist

  • the pull request title describes what this PR does (not a vague title like Update index.md)
  • the pull request targets the default branch of the repository (develop)
  • the code follows the established code style of the repository
    • npm run prettier:check passes
    • npm run lint:check passes
  • tests are added for the changes I made (if any source code was modified)
  • documentation added or updated
  • I have run the project locally and verified that there are no errors

Fixes

fixes #815

@MHekert MHekert changed the title exposed metadata storage feat: exposed metadata storage Nov 21, 2021
@vlad-ostrovski
Copy link

Any news on this?

@MHekert MHekert force-pushed the feat/exposed-metadata-storage branch from f73dd82 to daa46fe Compare October 18, 2022 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

feature: expose defaultMetadataStorage
2 participants