Add sentry_link for GraphQL

[ueman]

📜 Description

Resolves #1126

💡 Motivation and Context

Context: #1126 (comment)

💚 How did you test it?

It's already used widely in production without any reported issues

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• No new PII added or SDK only sends newly added PII if sendDefaultPii is enabled
• I updated the docs if needed
• All tests passing
• No breaking changes

🔮 Next steps

• Hand over the ownership of the https://pub.dev/packages/sentry_link package on pub
• Add CI for this new package (I would like to hand this task over to you)
• Rename the folder from sentry_link to just link or graphql?

Open questions

• What to do with the changelog? All other packages reuse the same one
  • Changelog has been moved and linked
• What to do with the license? I'm happy to change it

I'm happy to discuss this via Discord, Twitter, E-Mail, or whatever :D

[buenaflor]

thx!!

I wonder how we are going to port the existing changelog since we symlink the main changelog in our packages and I don't necessarily want to remove the existing graphql changelog

[ueman]

Yeah, I've wondered the same. Maybe keep it as CHANGELOG_OLD.md and then just link once from the shared one to it?

E.g. add the following to the new changelog:

### version xxx

- Transfer ownership to Sentry. To see the old changelog from previous versions go to [here](link/to/old/changelog.md)

or something like that.

[buenaflor]

thx, will get to this PR once the next sentry flutter release is out

[ueman]

@buenaflor Are there any updates?

[ueman]

This could be added to the default ones in the sentry package instead. However, I would prefer that to be done in a follow-up PR, to keep this PR essentially just as the take-over.

[ueman]

@buenaflor or @vaind any chances of moving forward with this? :D By download count if would be on the 6th place of all Sentry packages in the Dart ecosystem

[buenaflor]

can we change the folder namesentry_link -> link? to keep in line with the other namings

and

craft.yml still needs an entry link for the pub dev section

I will do the registry entry manually later (I need to add it to the sentry registry repo first after an initial release)

[ueman]

can we change the folder namesentry_link -> link? to keep in line with the other namings

Sure

craft.yml still needs an entry link for the pub dev section

I'll take a look at it.

[buenaflor]

Maybe we can also setup a simple CI for running the tests similar to hive.yml

nvm we can do this after the pr

[buenaflor]

@kahest do we need to look out for anything specific when transferring external repos to ours?

So far we:

• changed license to MIT
• old changelog is internally part of sentry_link for visibility
• new changes will just be part of the main changelog as usual

[ueman]

Handing over the package name on pub.dev still needs to be coordinated too.

[buenaflor]

for my understanding: since we'll use the same pubspec config, any new release will just update the sentry_link package directly right?

[ueman]

for my understanding: since we'll use the same pubspec config, any new release will just update the sentry_link package directly right?

Yeah, but I need to hand over the ownership of the "name" on pub.dev. Otherwise the upload will just fail

[buenaflor]

what about this

• we can merge this as is
• I'll set up CI and check if everything is running fine
• check code more in depth etc...
  • just a sanity check
• then when everything is clear we can do all the steps for uploading, e.g adding a target to craft, transfer ownership etc...

wdyt?

[ueman]

Sounds good. I'm happy to jump on call or something for the package transfer on pub. I guess that's easier than sending messages back and forth

[buenaflor]

sry, let's remove the craft targets for now, I'll do this manually after I've set up CI and so on

otherwise it will try to upload the package already when we run another release (which we might soon)

[ueman]

Done