Twitter import ignores default project, always saves to sm_project_twitter_bookmarks

[fyzanshaik]

Bug Description

When using the main "Import Bookmarks" button on x.com/i/bookmarks, tweets are always saved to the hardcoded sm_project_twitter_bookmarks container tag instead of the default project selected in the extension popup.

Steps to Reproduce

1. Open extension popup and select a custom project (e.g., "X Bookmarks")
2. Go to https://x.com/i/bookmarks
3. Click the "Import Bookmarks" button
4. Check the API call to /v3/documents/batch

Expected Behavior

Tweets should save to the selected default project's containerTag

Actual Behavior

Tweets always save to containerTags: ["sm_project_twitter_bookmarks"]

Root Cause

twitter.ts line 59 doesn't pass selectedProject parameter when calling BATCH_IMPORT_ALL, causing the importer to always use the fallback value.

Note

Folder imports work correctly because they do pass the selectedProject parameter.

[linear]

ENG-419

[MaheshtheDev]

reason for this @fyzanshaik that we don't want to bloat your current projects with x bookmarks. cause it will just make more mixture information in your project. i think much better approach would be asking in which project they want to save when they click on "Import Bookmarks"

We are already doing it for X bookmarks folder level import @fyzanshaik , can you refer that ?

[fyzanshaik]

@MaheshtheDev I see your point about the modal approach - that makes sense for consistency with folder imports.

However, there's still a bug: the main import currently ignores BOTH the default project selection AND doesn't show a modal. It just hardcodes to sm_project_twitter_bookmarks regardless of user choice.

My PR fixes it by respecting the default project (like page saves do), but I'm happy to change it to show a modal instead (like folder imports) if that's the preferred UX. Which approach should I implement?

Either way, the current behavior where it ignores user selection entirely needs fixing.

[MaheshtheDev]

@fyzanshaik this has been fixed and new version is released now

[fyzanshaik]

@MaheshtheDev checking sir good work!