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

Introduce nested paths #358

Closed
MateuszKubuszok opened this issue Sep 13, 2023 · 1 comment · Fixed by #377 or #419
Closed

Introduce nested paths #358

MateuszKubuszok opened this issue Sep 13, 2023 · 1 comment · Fixed by #377 or #419
Labels
dragons ahead Task which requires handwriting compiletime reflection for Scala2&3 and/or updating the architecture enhancement

Comments

@MateuszKubuszok
Copy link
Member

It's similar to what is planned in arainko/ducktape#74.

As a stepping stone, we might change how we represent field names to prevent breaking changes too often (it can be done before 0.8.0, then an actual work could be done later in a backward compatible way).

@MateuszKubuszok
Copy link
Member Author

Path representation was adjusted in #377 to allow work on this in the future 0.8.x releases.

@MateuszKubuszok MateuszKubuszok added the dragons ahead Task which requires handwriting compiletime reflection for Scala2&3 and/or updating the architecture label Oct 23, 2023
@MateuszKubuszok MateuszKubuszok linked a pull request Oct 25, 2023 that will close this issue
26 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dragons ahead Task which requires handwriting compiletime reflection for Scala2&3 and/or updating the architecture enhancement
Projects
None yet
1 participant