Skip to content

feat: id validation#404

Merged
azfoo merged 3 commits intodevfrom
id-validation
Mar 25, 2026
Merged

feat: id validation#404
azfoo merged 3 commits intodevfrom
id-validation

Conversation

@azfoo
Copy link
Collaborator

@azfoo azfoo commented Mar 17, 2026

also removes scanning through all of the current ids if no id is given.

@azfoo azfoo requested a review from FelipeDefensor March 17, 2026 22:34
Copy link
Collaborator

@FelipeDefensor FelipeDefensor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a clear improvement over my implementation. The only thing, apart from the comments, is that I am not sure we want to silently "adjust" conflicting IDs in the long term. A user might, for instance, write a script that creates a components with a hardcoded ID, and later use that ID to get the component for a future operation. That operation would misteriously fail if we changed the ID when creating the component without an error or warning. Since we are rather far from such an API in the moment, I am fine with going for what you propose, at least for now.

Base automatically changed from refactor-timeline-requests to dev March 20, 2026 12:28
azfoo added 2 commits March 20, 2026 18:28
also removes scanning through all of the current ids if no id is given.
@azfoo azfoo merged commit 174dc2b into dev Mar 25, 2026
11 checks passed
@azfoo azfoo deleted the id-validation branch March 25, 2026 12:50
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.

2 participants