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

feat: observation_level.order #701

Merged
merged 3 commits into from
Nov 6, 2024
Merged

feat: observation_level.order #701

merged 3 commits into from
Nov 6, 2024

Conversation

rdahis
Copy link
Member

@rdahis rdahis commented Nov 4, 2024

Ainda está com um problema: quando eu edito algum campo de metadado, parece que ele transforma o campo observation_level.order em None e aí dá erro por dizer que o campo é obrigatório.

@rdahis rdahis self-assigned this Nov 4, 2024
@rdahis
Copy link
Member Author

rdahis commented Nov 4, 2024

@mfagundes lembra quando criou essa possibilidade de order lá atrás?! Tem alguma ideia do que possa estar causando esse erro descrito ali em cima?

@rdahis rdahis changed the title feat: observation_level.order; working except when editing metadata f… feat: observation_level.order Nov 4, 2024
@rdahis rdahis linked an issue Nov 4, 2024 that may be closed by this pull request
3 tasks
@rdahis rdahis merged commit cf0b995 into dev Nov 6, 2024
3 of 4 checks passed
@rdahis rdahis deleted the feat/observation_level_order branch November 6, 2024 03:30
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

Successfully merging this pull request may close these issues.

Melhorias backend observation_level
1 participant