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

Problems with explicitAttrs and TimeInstan #1605 #1606

Closed
mapedraza opened this issue Apr 30, 2024 · 4 comments
Closed

Problems with explicitAttrs and TimeInstan #1605 #1606

mapedraza opened this issue Apr 30, 2024 · 4 comments

Comments

@mapedraza
Copy link
Collaborator

mapedraza commented Apr 30, 2024

Unexpected behaviour you saw

When using explictAttrs with value [] (no attribute should pass), TimeInstant value pass. See #1605

@AlvaroVega
Copy link
Member

corner case?

@fgalan
Copy link
Member

fgalan commented May 16, 2024

PR #1610 is the regression for this issue (i.e. when this issue gets fixed, the test included in that PR will check it). In fact, maybe this issue could be solved in task/add-533-func branch (the one used by PR #1610) so we have all in the same place.

@fgalan
Copy link
Member

fgalan commented Jun 6, 2024

I understand that after merging PR #1618 this issue can be closed.

@mapedraza
Copy link
Collaborator Author

I understand that after merging PR #1618 this issue can be closed.

That's right

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants