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

Make all _ fields private #333

Closed
HarelM opened this issue Sep 12, 2021 · 7 comments
Closed

Make all _ fields private #333

HarelM opened this issue Sep 12, 2021 · 7 comments
Labels
wontfix This will not be worked on

Comments

@HarelM
Copy link
Collaborator

HarelM commented Sep 12, 2021

Motivation

The motivation is to properly define all methods and members of classes with their appropriate modifier (public, private mainly).
This is a big challenge that requires a lot of work.
Having said that, doing it for _ prefixed fields and methods should be relatively simple and an easy win.

@rbrundritt
Copy link
Contributor

rbrundritt commented Sep 17, 2021

I wonder if this would break any workarounds people have implemented in production. In the past I've accessed these via the console to modify things to test and see if it addresses an issue I ran into.

@HarelM
Copy link
Collaborator Author

HarelM commented Sep 17, 2021

This is what 2.0 is for...

@drwestco
Copy link
Contributor

Unless the project is using a minifier that mangles private class member names (not common practice), marking members as private shouldn't affect such debug console hacks.

@douglasg14b
Copy link

This would break tons of workaround that people use.... I even have some of these kicking around.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Mar 28, 2022
@douglasg14b
Copy link

Oh boy, stale bot.

@github-actions github-actions bot removed the stale label Mar 29, 2022
@HarelM
Copy link
Collaborator Author

HarelM commented Aug 17, 2022

Unfortunately, due to the large echo system around maplibre I think this won't help anyone but only cause pain.
Having said that, I urge people who are using these private fields to open issues with API request changes/improvements so that they will be able to use fields that they need without the fear of things breaking...

@HarelM HarelM closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2022
@HarelM HarelM added the wontfix This will not be worked on label Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants