In the future, the following edge cases should be handled. In the prototype stage of the extension, they are rare occurrences and are not highly relevant.
File changes
- File is renamed: the cached
typestore data should react to the event accordingly by updating the cache
- File is moved: same as above
- File is deleted: remove cache
Edit events
In general, a mechanism will have to be devised on how the file cache will react when a file is changed. Should some annotations be invalidated, or the Type4Py server call re-triggered? (this should go into it's own issue later on, as it might require changes to the model, server and the client)
Additionally, the line numbers may be invalidated, rendering the cache incorrect (e.g. if all functions shift by 2-3 lines)
In the future, the following edge cases should be handled. In the prototype stage of the extension, they are rare occurrences and are not highly relevant.
File changes
typestoredata should react to the event accordingly by updating the cacheEdit events
In general, a mechanism will have to be devised on how the file cache will react when a file is changed. Should some annotations be invalidated, or the Type4Py server call re-triggered? (this should go into it's own issue later on, as it might require changes to the model, server and the client)
Additionally, the line numbers may be invalidated, rendering the cache incorrect (e.g. if all functions shift by 2-3 lines)