Closed theory-in-progress closed 1 year ago
Name | Link |
---|---|
Latest commit | a0cb360830be244d2523327fb5635bbd3dab511b |
Latest deploy log | https://app.netlify.com/sites/code-generator/deploys/64f6e64278ff830008296987 |
Deploy Preview | https://deploy-preview-312--code-generator.netlify.app/ |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Can you check if instead of parsing all files if we parse just the main.py
file does this feature work(as I think for all options there is always a change in main.py file) and what can be the time advantages ?
For the previous code where we hashed the store.config
we got a time difference around 1-2 milliseconds, but for the current PR Where we hash the whole code, we get a time difference of around ~5 milliseconds.
So considering this, if we hash only the main.py
that still would range between 1-5 milliseconds, not much time difference I would say...
store.config
and hashing of the whole code in the template.Additional context
Currently, uuid hashes only the current store.config, so any changes in store.config would change the uuid, but suppose we follow the steps:
What is the purpose of this pull request?