Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Firecms] Add support for typesense search #493

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

Open
yash1200 wants to merge 2 commits into firecmsco:main
base: main
Choose a base branch
Loading
from yash1200:typesense

Conversation

@yash1200
Copy link

@yash1200 yash1200 commented Apr 12, 2023

This PR adds supports for typesense search and also add yarn.lock file to gitignore.

Copy link
Contributor

@SeeringPhil SeeringPhil May 2, 2023

Choose a reason for hiding this comment

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

Depending on how Camberi are deploying and what their CI/CD looks like, yarn.lock might actually need to be committed to the repo so I'm not sure that this change will be accepted if you mess with that 🤔

@fgatti675

Copy link
Member

@fgatti675 fgatti675 May 3, 2023

Choose a reason for hiding this comment

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

That is correct, yarn.lock should not be excluded from Git

"react-router": "^6.2.0",
"react-router-dom": "^6.2.0"
"react-router-dom": "^6.2.0",
"typesense": "1.5.3"
Copy link
Member

@fgatti675 fgatti675 May 3, 2023

Choose a reason for hiding this comment

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

Could you move this dependency to peer dependencies?
So that only users who want to use it can pull it in.
Thanks!

Copy link
Contributor

@yash1200 Hello! Is this ready to merge?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fgatti675 fgatti675 fgatti675 left review comments

+1 more reviewer

@SeeringPhil SeeringPhil SeeringPhil left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /