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

fix: added skipBotEvents options in the manifest.ts type #54

Closed
wants to merge 1 commit into from

Conversation

gentlementlegen
Copy link
Member

@gentlementlegen gentlementlegen marked this pull request as ready for review January 20, 2025 13:25
Comment on lines +17 to 19
"ubiquity:skipBotEvents": T.Optional(T.Boolean({ default: true })),
configuration: T.Optional(T.Record(T.String(), T.Any(), { default: {} })),
skipBotEvents: T.Optional(T.Boolean({ default: true })),
Copy link
Member

Choose a reason for hiding this comment

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

skipBotEvents is already present. I'm not even sure what's the benefit of following the manifest standard so strictly, then configuration should also be ubiquity:configuration since it's not in the standard.

Copy link
Member Author

Choose a reason for hiding this comment

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

I didn't notice it thanks for pointing it out. It was to stick to our format but I do agree that I do not see much benefit either, we are not running a web extension. Will close this, all the other pull-requests with the updated manifest are open.

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.

Investigate skipBotEvents always true even when defined false in the configuration
2 participants