Resource Tagging #9367
Merged
Resource Tagging #9367
Conversation
This file contains 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
improve file properties panel
…into resource-tagging
…into resource-tagging
…into resource-tagging
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
HexaField
requested changes
Dec 21, 2023
barankyle
reviewed
Dec 21, 2023
fully restore fetch projects
fully import all resource fields
add localization add "remove tag" button remove null fields when serializing resources.json correctly handle non-resource files in file properties panel
automatically regenerate resources.json whenever a file is changed or uploaded
22 tasks
…into resource-tagging
Rezmason
pushed a commit
that referenced
this pull request
Dec 26, 2023
* seed static resources with project assets improve file properties panel * licensing * checkpoint * generate .sql file for project static resources * working tagging UI in File Browser * licensing * switch from .sql to .json resources file * re-async _fetchDevLocalProjects * remove pagination fully restore fetch projects * wipe URL from manifest files fully import all resource fields * add check for existing id * fix key corruption add localization add "remove tag" button remove null fields when serializing resources.json correctly handle non-resource files in file properties panel * close file properties on save changes automatically regenerate resources.json whenever a file is changed or uploaded * undo hardcoded visible back button * increase pagination count in existing asset query * fix eslint errors * use key instead of id to detect duplicate resources * remove pagination on project-helper * fix duplicate resources generated on npm run dev locally * use useFind in FilePropertiesPanel * remove mysqldump from server package.json
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
In preparation for the Assets Panel, we need to tag all assets in every project with appropriate categories.
This PR introduces a UI for manually adding tags, as well as crude auto-tagging based on asset class.
Also, static resources is now automatically seeded with every valid project asset on project upload.