Yeah, it is possible! You just need to intercept the inputProps params on the network tab when you hit "Render". Then follow the instructions on Remotion's website and pass the inputProps there
@just-moh-it
I Live to create better apps everyday
I'm an indie developer based out of my home, lol, and love to create awesome applications. People call me picky for adding extra attention to detail and over-doing stuff, while sometimes I feel like Jerry-Rigging everything I make
I'm open to productive open source development and collaborations
Yeah, it is possible! You just need to intercept the inputProps params on the network tab when you hit "Render". Then follow the instructions on Remotion's website and pass the inputProps there
Cool extension! Was able to skip the hassle of posting threads manually within a minute 🤩 With a little polishing and a few features, it could become a very strong competitor to paid tools like Typefully! Beautiful code as well 😃
Rounak Singh I understand your concern. I've fully made sure to not change any noticeable functionality of the application. Just that I wanted to track the clicks I was getting, so I added analytics. Some people reported some typos, so I changed some text. Just had a few complaints of errors not showing up if progress is struck, fixed that. Most of them because I went with JavaScript for this project, not TypeScript. You could even see the commit messages and have a look at the changes, they're mostly silly typos or updating mundane-stuff. I believe I do not stand an unfair chance with making any of the changes, and besides, these commits contribute to less than 1% of the code (the 5k+ additions is git's problem that it does not differentiate renames with changes. Like if I change the name of the src file to source , it would show 99% lines added, 99% deleted. These changes show because I renamed a template from fancy presentation to angular presentation to make it sound more descriptive, and also renamed some SVG files). If you do not agree, you're free to go back to the commit on 30th June and report any noticeable changes you find you feel are unfair to submit after the deadline. This does not change the fact that the project was full functional, completed and submitted even a few days before the deadline. As I said before, feel free to go back to any commit you feel makes a significant change in my project's marking. Git is a very transparent technology, and it's up to the judges to decide which codebase to consider. I do not agree with how altering less than a few typos and minor stuff could result in respect changes when the project is so huge 😃. Thanks!
Rounak Singh I know. You could check the commit till 30th of June, the app was already fully complete. The only things I changed after the date are either visual improvements like adding the play button on the homepage video, adding analytics, license, or changing the default text in some template, nothing functionality wise. You're free to only consider the repo that was available on the 30th. You won't find any noticeable difference. Just that the product is used by me very frequently, so I try to improve it a little, every time I notice something, even after the hackathon ends. I did the same with Pckd (for the Netlify hackathon), and now it's one of the top open-source URL-shortener projects. I hope that won't be a problem now? 😃