Skip to content

Conversation

aaronArinder
Copy link
Contributor


Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

  • PR description explains the motivation for the change and relevant context for reviewing
  • PR description links appropriate GitHub/Jira tickets (creating when necessary)
  • Changeset is included for user-facing changes
  • Changes are compatible1
  • Documentation2 completed
  • Performance impact assessed and acceptable
  • Metrics and logs are added3 and documented
  • Tests added and passing4
    • Unit tests
    • Integration tests
    • Manual tests, as necessary

Exceptions

Note any exceptions here

Notes

Footnotes

  1. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this.

  2. Configuration is an important part of many changes. Where applicable please try to document configuration examples.

  3. A lot of (if not most) features benefit from built-in observability and debug-level logs. Please read this guidance on metrics best-practices.

  4. Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions.

@aaronArinder aaronArinder requested a review from a team as a code owner September 8, 2025 20:25
@aaronArinder aaronArinder marked this pull request as draft September 8, 2025 20:25
@apollo-librarian
Copy link

apollo-librarian bot commented Sep 8, 2025

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: 75eb3d32e0b1f67dfad4cac8
Build Logs: View logs

Copy link
Contributor

github-actions bot commented Sep 8, 2025

@aaronArinder, please consider creating a changeset entry in /.changesets/. These instructions describe the process and tooling.

Comment on lines +45 to +47
private: Private @join__field(graph: SUBGRAPH_A) @policy(policies: [["admin"]])
public: Public @join__field(graph: SUBGRAPH_A)
opensecret: OpenSecret @join__field(graph: SUBGRAPH_A)
Copy link
Member

@lrlna lrlna Sep 9, 2025

Choose a reason for hiding this comment

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

we want another test that has a field defined like this. this the one that we are unsure about (although all the other ones are excellent to test as well 🙏 ):

Suggested change
private: Private @join__field(graph: SUBGRAPH_A) @policy(policies: [["admin"]])
public: Public @join__field(graph: SUBGRAPH_A)
opensecret: OpenSecret @join__field(graph: SUBGRAPH_A)
private: Private @join__field(graph: SUBGRAPH_A) @policy(policies: [["admin"]])
public: Public @join__field(graph: SUBGRAPH_A)
opensecret: OpenSecret @join__field(graph: SUBGRAPH_A)
secure: Secure @join__field(graph: SUBGRAPH_A)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ptal; I think it's good now?

private: Private @join__field(graph: SUBGRAPH_A) @policy(policies: [["admin"]])
public: Public @join__field(graph: SUBGRAPH_A)
opensecret: OpenSecret @join__field(graph: SUBGRAPH_A)
secure: Secure @join__field(graph: SUBGRAPH_A)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

line where secure was added (@lrlna)

@aaronArinder aaronArinder changed the title DRAFT: playing around with @policy and interfaces chore(tests): backfilling tests for the @policy directive Sep 22, 2025
@aaronArinder aaronArinder marked this pull request as ready for review September 22, 2025 19:48
@aaronArinder aaronArinder force-pushed the aaron/policy-debugging branch 5 times, most recently from 18c1e35 to 3c061db Compare September 23, 2025 13:23
@aaronArinder aaronArinder requested a review from lrlna September 23, 2025 13:23
@goto-bus-stop goto-bus-stop self-requested a review September 24, 2025 14:28
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.

2 participants