Skip to content

feat!: drop unused Metrika goals, hardcoded services, and unused schema utils - #333

Open
niktverd wants to merge 9 commits into
nextfrom
chore_stuff
Open

niktverd wants to merge 9 commits into
nextfrom
chore_stuff

Conversation

@niktverd

Copy link
Copy Markdown
Contributor

No description provided.

@niktverd
niktverd requested a review from NikitaCG as a code owner August 31, 2026 11:12
@gravity-ui-bot

Copy link
Copy Markdown
Contributor

Preview is ready.

@gravity-ui-bot

Copy link
Copy Markdown
Contributor

Playwright Test Component is ready.

@niktverd
niktverd requested a review from aeksandla August 31, 2026 12:23
- Removed the `BlogConstructorProvider.analytics` prop; analytics should now be passed through the `settings` prop on `BlogPage` and `BlogPostPage`.
- Updated analytics event handling to use the new `createExtendedEvent` utility for better integration with Blog Constructor goals.
- Adjusted various components (Banner, CTA, Header, Meta, etc.) to reflect the new analytics structure and ensure proper event emission.
- Updated documentation to guide users on the new analytics configuration and usage.
- Bumped dependencies for `@gravity-ui/page-constructor` and related packages to the latest versions.
Comment thread src/constructor/README.md
```

**!!! Important thing** - We throw analytics settings in blog constructor provide, if we need analytics from only-blog components. If we need analytics in page-constructor blocks we need to throw analytics settings in [page settings props](../containers/BlogPage/README.md)
`BlogConstructorProvider` does not provide analytics. Pass the single analytics configuration via

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

if does not provide, maybe we need delete this article ?

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.

3 participants