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

UnsupportedProperties as static field #607

Open
jansule opened this issue Nov 21, 2023 · 1 comment
Open

UnsupportedProperties as static field #607

jansule opened this issue Nov 21, 2023 · 1 comment

Comments

@jansule
Copy link
Contributor

jansule commented Nov 21, 2023

Feature Request

Is your feature request related to a problem? Please describe.

It would be great to have the unsupportedProperties as static property instead of an instance property. This would allow to use the unsupportedProperties property without having to instantiate a parser.

Describe the solution you'd like

--

Describe alternatives you've considered

--

Additional context

--

@KaiVolland
Copy link
Contributor

As an less invasive alternative we could move the value of the unsupported properties in every parser to its own variable outside of the parser class.

The class could then reuse it and the variable could also be exported.

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