In general, revision control and collaborative development features are top of mind for me in terms of future opportunities.
I am sure you all have already thought about this (this may have even existed in the past) but I think integrating any custom code component or other JS code with Github could be really valuable.
I obviously don’t know the details but it seems that the Javascript editor is the same throughout all areas of Backendless (custom code Codeless blocks, cloud code areas, etc.) The same editor may also be used for the CSS/LESS theme editor. It would be awesome if each of these could be synced to a file in a Github repo. The user wouldn’t even have to control the file structure either - you guys might be able to do the sync at the app level as long as each instance of the editor had a corresponding file in the repo and could easily be found.
Then people could edit the code in that repo, collaborate as normal with branching and all the other benefits of git, and the Backednless site would simply always take the most recent commit at the time of publication or preview.
Hi @James_Hereford ,
Thank you for this interesting proposal, which requires a balanced, thoughtful decision, I will create a ticket to discuss it with my colleagues. And I’ll be back soon with an answer.
Regards,
Sergey
Hi @James_Hereford
Thank you for your suggestion regarding GitHub integration for code synchronization. While we appreciate the idea, we’ve concluded that implementing a complete Git version control system may not be practical for us at this time.
We value your input and encourage you to keep sharing your ideas with us.
Best regards,
Sergey
No worries, thank you for considering! My general thought was actually not to implement git.
People using this would edit in vscode or elsewhere. The only thing needed in the Backendless editor is to be able to sync and pull the latest code from the repo. Two way sync would be great but I think you’re correct that in that case you’d effectively be implementing git.
Either way, just wanted to share the thought. I know you guys have a lot in the pipeline but revision controls and collaborative development tools are hopefully on the list somewhere.
Thanks!
-James
If things were only that simple. It would need to deal with conflicts, handle authentication and login failures, have some kind of logic for account errors. It quickly can become a significant effort just to handle the most basic scenario.
Makes sense. Thanks for considering!