Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing gauge as length unit #149

Open
jeromevalentin opened this issue Jul 17, 2024 · 3 comments
Open

Missing gauge as length unit #149

jeromevalentin opened this issue Jul 17, 2024 · 3 comments

Comments

@jeromevalentin
Copy link

Gauge unit is used in US to measure really thick products like plastic film.

As defined here: [gauging.com] (https://www.gauging.com/customer-resources/film-calculators/plastic-gauge-thickness-chart/)

100 gauge = 1 mil = 0.0000254 m

@glepretre
Copy link
Contributor

The problem with Gauge is that each profession has its own gauge unit to measure anything and everything. This would be impossible to implement correctly unless you named each "gauge" precisely.

Have a look a the list here: https://en.wikipedia.org/wiki/Gauge. The plastic film use case is not there by the way.

I guess your need would be to add it to the library as "custom" unit: #96

It seems that unitmath supports it 😉

@jeromevalentin
Copy link
Author

@glepretre Thanks for your comment ! You are right such "missing units" are probably business dependant.

So the remaining question is:

When the possibility to define custom unit will be really added to the main library?

The PR (#112) is still not integrated 3 years after .... what is blocking the integration process?

We can see that the feature is really missing and some developers are starting to fork to integrate this PR ... (like philippspohn@a55472f).

Should we stop using @gentooboontoo version ?

Thanks in advance for any hints.

@glepretre
Copy link
Contributor

When the possibility to define custom unit will be really added to the main library?

When @gentooboontoo will be convinced of the benefits of this feature compared to the drawbacks: for example as long as it is not possible, users ask for the addition of new units in the library, often legitimate.

But if a clean and convincing Pull Request was made, for example by also documenting the fact of continuing to ask for the addition of units recognized as missing; with tests, etc. I think we could convince @gentooboontoo.

The PR (#112) is still not integrated 3 years after .... what is blocking the integration process?

The PR has been closed by its author, after the first review.

We can see that the feature is really missing and some developers are starting to fork to integrate this PR

The issue #96 is still open to discuss and suggest a new PR.

Should we stop using @gentooboontoo version ?

It's open-source: you can do whatever you want 😅 As a developer I would recommend to contribute to this library because it's still maintained by @gentooboontoo but you can you another one, or fork, but this would not profit to the js-quantities users 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants