Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, this is the first of a series of improvements I've been playing around with in my fork. This addition allows users to press a button to generate the BuildConstants file for a selected build without automatically matching their Editor settings (such as the build scenes, product name, etc.) to the selected build:
In order to create this commit, I cherry-picked the feature out of my dev branch and squashed it down. Coincidentally, this commit would've also added the scripting backend and "Generated" namespace to the BuildConstants file but I saw that it was already completed independently! It was a really similar implementation to how I was doing it, so I conformed to the approach used in the base project. I will also try and backport this and the other recent changes into my fork for easier cross-compatibility and git comparisons in the future.
As always, let me know if you have any suggestions or concerns and I'm happy to make any updates needed. Thanks!