BabylonJS / BabylonJS/Exporters

Installer improvement suggestion

Open
#899 1 comment 1 reaction 0 assignees View on GitHub
enhancement help wanted Installer
Dominant language
Wolfram Language
Stars
704
Forks
322
PR merge metrics
No merged PRs in 30d

Description

Hello,

I'm writing a suggestion concerning the installer.

Using the exporter on a daily basis, it's important for me to keep the exporter up to date and functioning.
One day, however, I had a problem with an update of the exporter that wouldn't let me export. I tried to go back to a previous version, but it was tedious manually and I lost a lot of time.

What I suggest is that instead of having the installer automatically installing the latest version, maybe make an installer that installs only the version from when it was posted on GitHub. This way, if I want to go back to an earlier version, I just have to download the old installer on GitHub.

An alternative would be to select which version of the exporter you want to install directly on the installer. That could be even better since we wouldn't have to download another installer, and it would automatically check the versions available.

I hope you find this suggestion helpful.

Contributor guide

No contributing guide indexed for this repository

Research direction

No installer files, tests, or entry points are named. Start by locating the exporter's installer and version-release workflow, then clarify whether version-pinned installers or in-installer version selection is intended. Done would mean a user can install or return to a chosen exporter version without manual replacement.

Written by the indexing model from the issue text.

Assessment

Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.