-
Notifications
You must be signed in to change notification settings - Fork 2
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
Print extensions and modifierExtensions before stripping them #346
Comments
Or... maybe in the case of extensions, it's better to leave them in place, but remove all content. So they just have the Unknown modifierExtensions do currently get printed to the console, one per line. So it's a little noisy. But workable for now. So maybe an MVP of this ticket is: "stop erasing extensions entirely, just erase their content, leave the url in place" |
Jamie was nervous enough about including even a whiff of arbitrary extensions (and the more complicated de-id story of "well, we mostly strip extensions", that current thinking is to go back to just logging these on the console. |
This way a user can still get a sense of what extensions are in use / what they are missing. And then they can investigate further / submit a ticket for support for the extension as needed.
Maybe just print a number of resources with the extension, like so:
The text was updated successfully, but these errors were encountered: