you can put an invalid file, like if you rename a .png file to a .jpeg one. It's a jpeg, but invalid
Oh yeah that's a good point too!
Do you have any idea on when the @Asset and @Options annotations will be added?
I'm not sure what the latest estimate is 
I know they were trying to get all of the GSoC projects out by the end of the year, but the core team been really busy working on iOS stuff. I think the plan is to include everything in the next release (whenever that may be)? But @ewpatton may have more info for you.
Or is it possible to use your open source code to make it in my extension?
Sadly not To put it simply there are only certain APIs/areas that extensions can access, so there's certain things they can't do. For example, extensions specify how to what blocks they want to provide using the @SimpleEvent, @SimpleProperty, etc annotations. They can't create blocks "manually".
However, changes to the core code /can/ do access more things. Which is what my pull request does.
I'm a bit excited about it!
Hehe I'm excited about it too! Hopefully extension developers find it useful =)
If you know a bit about git you should be able to try it out:
- Pull down the changes introduced by my pull request.
- Add the relevant annotations to your extension.
- Rebuild your extension.
- Test it out on the gsoc2020 test server.
If you do decide to try it, please tell me how it goes! If there are any problems I definitely want to fix them hehe.
Best wishes,
--Beka