You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can look into this--for now the Skip team takes a large role in most of the integrations so we're pretty comfortable with weaving these components into the existing app structure. The other consideration is that each app is in general structured differently and can potentially be constructed differently w/r/t depinject, etc. so it's likely that 1 size fits all wouldn't track very well in practice here.
Referencing: https://github.com/skip-mev/connect/blob/main/docs/developers/integration.mdx
I'd like to make a suggestion that I think will make connect much easier to integrate.
Currently, in the docs we have:
providing these files in their complete form, for use as pasta, is likely the best way to present the integration step of the process.
After that, there could be another document:
Referencing: https://github.com/skip-mev/connect/blob/main/docs/developers/customization.mdx
and in the customization document, we could guide developers through any possible tweaks.
The text was updated successfully, but these errors were encountered: