-
Notifications
You must be signed in to change notification settings - Fork 51
[Meta Provider] Overview of Meta Provider #1277
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
Comments
You can put the plan(SSDC-AndroMETA#4) here too :-D |
just arrived~😊 |
Could you guys check the done-lists here? |
Thanks for your guys' hard works :-D. BTW, I found the draft #1349 has a little bug. It doesn't show the relation properly, only a single node exists even if I generated a circle from the tflite. If you can, could you revise the draft, and also provides some unit tests? |
Thank you for your comments of this works. We already recognize the similar problem. Can you check if the input/output path of config file(.cfg) is relative path? We think the bug occurs when the input/output path of config file(.cfg) is relative path not absolute path. |
Uh oh!
There was an error while loading. Please reload this page.
Hello, we are team AndroMETA from SSAFY (Samsung SW Academy For Youth).
What
We suggests adding meta provider to one-vscode extension.
Meta provider is a feature to provide information for each files. (#1240)
This contains three parts: Metadata viewer, Relation viewer, Metadata management.
Why
ONE Explorer offers limited information about files. The tree view of it depends on the configuration files only.
So that we think we need to store unchanged key information of files and make a method to access them anytime, anywhere.
How
1. Metadata is saved and managed using external hash object files.
2. Metadata viewer show the key information of the file as a web view.
3. Relation viewer show the relationship of files using tree structure.
Our plan
Work List:
Metadata Viewer
Relation Viewer
Metadata Manager
Event Management
The project plan will be continuously updated.
The text was updated successfully, but these errors were encountered: