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

[Property Editor] Tests to make sure our constants are in-sync with those in the analysis_server #8824

Open
elliette opened this issue Jan 29, 2025 · 0 comments
Labels
P2 important to work on, but not at the top of the work list. property editor testing

Comments

@elliette
Copy link
Member

DevTools relies on keeping some of our constant values in sync with those in the analysis_server:

See for example:

This could be accomplished by fetching the raw contents of the file from the Dart SDK repo on Github. However, I believe the requests will be rate-limited to 60/hour unless we authenticate with a Github token.

We should either 1) create a Github token secret we can use for these tests 2) schedule the tests to only run daily so as not to exceed the rate limit

@elliette elliette added P2 important to work on, but not at the top of the work list. property editor testing labels Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 important to work on, but not at the top of the work list. property editor testing
Projects
None yet
Development

No branches or pull requests

1 participant