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

Move dependency on extended_email_reply_parser into the Conversations gem #999

Closed
jagthedrummer opened this issue Dec 26, 2024 · 0 comments · Fixed by #1002
Closed

Move dependency on extended_email_reply_parser into the Conversations gem #999

jagthedrummer opened this issue Dec 26, 2024 · 0 comments · Fixed by #1002

Comments

@jagthedrummer
Copy link
Contributor

For some reason extended_email_reply_parser is listed as a dependency on the main bullet_train gem, but it's not actually used anywhere in core or the starter repo. It seems like it was added to make the conversations gem work, but I'm not sure why it was added to bullet_train and not that gem.

extended_email_reply_parser depends on charlock_holmes which is very finicky to install due to native dependencies. Lots (possibly a majority?) of the problems that people run into getting Bullet Train running have to do with installing charlock_holmes. Removing it as a dependency in core should make things easier for people just starting out.

jagthedrummer added a commit that referenced this issue Dec 30, 2024
For some reason `extended_email_reply_parser` was added as a dependency
to the main `bullet_train` gem even though it's not used anywhere in
`core` or in the starter repo.

It _is_ used by `bullet_train-conversations` and is declared as a
dependency there, so we don't need it here.

`extended_email_reply_parser` relies on `charlock_holmes` which is
notoriously finicky to install due to native extensions. Removing this
dependency should eliminate one of the big problems that people often
run into when first setting up Bullet Train.

Fixes #999
jagthedrummer added a commit that referenced this issue Dec 30, 2024
For some reason `extended_email_reply_parser` was added as a dependency to the main `bullet_train` gem even though it's not used anywhere in `core` or in the starter repo.

It _is_ used by `bullet_train-conversations` and is declared as a dependency there, so we don't need it here.

`extended_email_reply_parser` relies on `charlock_holmes` which is notoriously finicky to install due to native extensions. Removing this dependency should eliminate one of the big problems that people often run into when first setting up Bullet Train.

Fixes #999
jagthedrummer added a commit that referenced this issue Dec 30, 2024
* Remove `extended_email_reply_parser` dependency

For some reason `extended_email_reply_parser` was added as a dependency to the main `bullet_train` gem even though it's not used anywhere in `core` or in the starter repo.

It _is_ used by `bullet_train-conversations` and is declared as a dependency there, so we don't need it here.

`extended_email_reply_parser` relies on `charlock_holmes` which is notoriously finicky to install due to native extensions. Removing this dependency should eliminate one of the big problems that people often run into when first setting up Bullet Train.

Fixes #999

* Oops missed one

* Need to define another teplate method

* linter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant