Skip to content

Conversation

@jamietanna
Copy link
Member

Although originally to fix #1638, which isn't a very recommended
approach as it may lead to a confusing behaviour for users, we can still
add support.

However, we should hide this behind both a global Compatibility Option,
to ensure that it's clearly opted-in, as well as adding a per-field
level to ensure that only the right fields are overridden.

Closes #1638.

Although originally to fix #1638, which isn't a very recommended
approach as it may lead to a confusing behaviour for users, we can still
add support.

However, we should hide this behind both a global Compatibility Option,
to ensure that it's clearly opted-in, as well as adding a per-field
level to ensure that only the right fields are overridden.

Closes #1638.
@lukasbash
Copy link

Got an ETA of a merge?

@jamietanna jamietanna merged commit 23e3721 into main Jul 21, 2024
@jamietanna jamietanna deleted the feat/unexported branch July 21, 2024 18:02
@jamietanna
Copy link
Member Author

(Merging as I had a bit of time this evening, not necessarily related to the bump)

@jamietanna jamietanna added the enhancement New feature or request label Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unexported fields not working anymore since v2.2.0

3 participants