Skip to content

fix: Minor Airdrop fixes #200

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

Merged
merged 3 commits into from
Apr 7, 2025
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions fern/docs/pages/airdrop/getting-started.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,9 @@ consider gathering the following information:
### Sync unit

A _sync unit_ is one self encompassing unit of data that is synced to an external system. Examples:
- Jira project
- SalesForce
- Zendesk
- A project in Jira.
- An account in SalesForce.
- An organization Zendesk.

### Sync run

Expand Down
2 changes: 1 addition & 1 deletion fern/docs/pages/airdrop/metadata-extraction.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ During the metadata extraction phase, the snap-in must provide an
This file provides a structured way of describing the external system's domain model,
including its domain entities, types, relationships, and other metadata.

You can check which object types for Airdrop DevRev supports [here](/snapin-development/airdrop/supported-object-types).
You can check which object types for Airdrop DevRev supports [here](/public/snapin-development/airdrop/supported-object-types).

## Triggering event

Expand Down
2 changes: 1 addition & 1 deletion fern/docs/pages/airdrop/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,6 @@ DevRev provides a range of snap-ins available through the DevRev marketplace for
various external systems like Jira and Zendesk. Sometimes, a specific snap-in may not be available
for a given external system. This is why DevRev enables creation of external connectors (extractors
and loaders) to other developers, allowing them to integrate with DevRev’s Airdrop and develop their
Airdrop own snap-ins.
own Airdrop snap-ins.

You can learn more about Airdrop in the [general documentation](https://docs.devrev.ai/import#airdrop-features).
4 changes: 2 additions & 2 deletions fern/docs/pages/airdrop/snap-in-examples.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
You can find snap-in examples for various external systems [here](https://github.com/devrev/adaas-connector-examples).
You can find snap-in examples for various external systems [here](https://github.com/devrev/airdrop-examples).

Examples include:
Examples currently include:

- Asana
2 changes: 1 addition & 1 deletion fern/docs/pages/airdrop/snap-in-template.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ It provides features such as:

If you check the template, you can see that a snap-in is a Node.js project with a specific file structure:

```
```yaml
- manifest.yaml
- code/
- scripts/
Expand Down
Loading