-
Notifications
You must be signed in to change notification settings - Fork 18
feat: add slugified filenames with short hash suffix for entity keys #367
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
feat: add slugified filenames with short hash suffix for entity keys #367
Conversation
|
Thanks for the pull request, @dwong2708! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
ormsbee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick turnaround on this! I have a few low-level requests. At a higher level, please also include a test showing what happens in potential identifier name collision, e.g. two identifiers that differ only by case.
ormsbee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few small requests. Thank you!
|
|
||
| def test_slugify_hashed_filename_special_chars(self): | ||
| # Test the slugify_hashed_filename function with special characters | ||
| self.assertEqual(slugify_hashed_filename("my@ex#ample!"), "myexample_3366b5") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "/" and ":" characters are also likely to show up in identifiers at some point (they already do so for components), so please test for those characters in particular.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Applied. Thanks
| self.assertEqual(slugify_hashed_filename("mY_eXamPle"), "my_example_d28c02") | ||
| self.assertEqual(slugify_hashed_filename("My_ExAmPlE"), "my_example_79232e") | ||
| self.assertEqual(slugify_hashed_filename("mY_EXAMPLE"), "my_example_b91dc0") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think you're actually testing anything different with these last few examples?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, I was just curious about different letter case scenarios. However, I changed it to only one check.
| - Append a short hash for uniqueness. | ||
| - Result: human-readable but still unique and filesystem-safe filename. | ||
| """ | ||
| slug = slugify(identifier) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we'll want to allow identifiers to use Unicode chars, as long as they are legal on the filesystem, i.e. we should call slugify(identifier, unicode=True)
Please add a test for that as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Resolves: #358
Context
When mapping identifiers directly to the file system, we run into several blockers:
Proposed Solution
Adopt a hybrid filename strategy that combines:
Example Mapping
My:Component → my_component_a12f4c.toml
My/Component → my_component_b91d0e.toml
This approach balances human readability with system safety.
Acceptance Criteria