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

Dework integration #1

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Dework integration #1

wants to merge 1 commit into from

Conversation

davidfant
Copy link

No description provided.

@davidfant davidfant marked this pull request as draft January 26, 2022 00:40
public function up()
{
Schema::table('circles', function (Blueprint $table) {
$table->string('dework_organization_id')->nullable();

Choose a reason for hiding this comment

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

I think a separate table with many-to-one support for external integratinos would be a more reusable model. Allowing for any number of external integrations.

Copy link

Choose a reason for hiding this comment

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

idk, if it is only one field...

I think it would attach to the protocol table

Is this id secret at all? if not, easier as we don't have to think about permissions for it.

And then, I wonder how the permissions work once in coordinape, the user needs an access token for both front ends.. hm

And like Zashton noted in coordinape discord:
This also needs to happen in hasura, as that is handling our migrations now

@exrhizo
Copy link

exrhizo commented Jan 31, 2022

Cool!

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

Successfully merging this pull request may close these issues.

3 participants