Skip to content

Conversation

@D4n2021
Copy link

@D4n2021 D4n2021 commented Nov 15, 2025

As most of us AMO devs likely don't even want to implement any type of data collection, added the most common mandatory option ("required": ["none"]) for us AMO devs to the top for much easier finding

…ev cases

As most AMO devs likely don't even want to implement any type of data collection, added the most common mandatory option  ("required": ["none"]) for us AMO devs to the top for much easier finding
Copy link
Collaborator

@rebloor rebloor left a comment

Choose a reason for hiding this comment

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

@D4n2021 you've now presented a specific example of the data_collection_permissions (that is for "no data collection") before the more general introduction to the key (under Personal data). Similarly, you mention that technical interaction data "be behaves differently from all other data types" before having introduced the behavior of the other data types. Issue such as these need to be accounted for in the restructuring.

@D4n2021
Copy link
Author

D4n2021 commented Nov 17, 2025

@rebloor ooooh oops, sorry! Do you have time to fix that? 😬 Sorry. 😕

@D4n2021 D4n2021 requested a review from rebloor November 17, 2025 14:46
@D4n2021
Copy link
Author

D4n2021 commented Nov 17, 2025

grafik

Sorry, didn't intend to, misclicked.

@rebloor
Copy link
Collaborator

rebloor commented Nov 17, 2025

@D4n2021 I can look at this when I finished come other changes

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants