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

Handle unexpected AVL IDs in a payload in a better way #26

Open
pankalog opened this issue Jan 8, 2025 · 0 comments
Open

Handle unexpected AVL IDs in a payload in a better way #26

pankalog opened this issue Jan 8, 2025 · 0 comments
Assignees

Comments

@pankalog
Copy link
Member

pankalog commented Jan 8, 2025

Related to #25

Ideally, should be handled by logging to the user that an AVL ID was not found in the provided parameter map, and that they should figure out what that does.

Then, a new attribute with the AVL ID as its name should be created, and the value type should be ValueType.TEXT. The issue that arises there, is that changing the ValueType of an attribute without deleting the previous attribute, could create some issues down the line. Overthinking? Maybe.

@pankalog pankalog self-assigned this Jan 8, 2025
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

No branches or pull requests

1 participant