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

Don't allow top level fields with the same name #519

Open
shcheklein opened this issue Oct 18, 2024 · 0 comments
Open

Don't allow top level fields with the same name #519

shcheklein opened this issue Oct 18, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@shcheklein
Copy link
Member

Motivated by this: #510 (comment)

I'm not sure it should be allowed at all - to have a nested column meta and a regular field meta at the same time. Would it be a deal breaker for the scenario if we put a limitation like that @tibor-mach ?

caveats:

  • if it's not too complicated to implement - ideally if it can be isolated in a single place)
  • let's do a bit of research - e.g. does pandas allow for this? if yes, we can get back to the original ticket and see how we should clarify the semantics of operations like select in this case Bug: hierarchical columns and the .select method #510 (comment)
@shcheklein shcheklein added the enhancement New feature or request label Oct 18, 2024
@skshetry skshetry self-assigned this Oct 29, 2024
@skshetry skshetry removed their assignment Nov 5, 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

No branches or pull requests

2 participants