-
Notifications
You must be signed in to change notification settings - Fork 13
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
Metadata #18
Comments
I think it might be safer to use some JSON metadata or any other format that prevent manual parsing. I am seing the use of |
The metadata parser was already built and works as expected. It regex targets the metadata header and then parses the JSON inside as expected. |
I think the steps for solving this would be to start using the SDK that has it built-in, so it doesn't need to be manually added to this plugin. |
I think this can be closed since we are now using the SDK and the metadata is handled there. |
This should be standardized in our SDK but we can do a manual implementation here. The metadata header schema is as follows:
CLASSNAME
a developer defined "class name" that can provide useful context of what operation is being performed.FUNCTION_CALLER
the name of the function that was run. Could be useful to start investigation for debugging.REVISION
no longer works, but was supposed to be a revision hash.Now, I think it makes sense to do something like:
Originally posted by @0x4007 in ubiquity-os-marketplace/text-conversation-rewards#97 (comment)
The text was updated successfully, but these errors were encountered: