We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, we support a model_file option in addition to model for users who prefer to edit their model in a separate file.
model_file
model
We should support a tuple_file that does the same for tuples.
tuple_file
That file will be the same format as accepted by write
write
name: Some Store model_file: ./model.fga tuple_file: ./tuples.yaml tests: - name: test 1 tuple_file: ./test1_tuples.json check: ... list_objects: ... - name: test 2 tuple_file: ./test2_tuples.json check: ... list_objects: ...
This follows on the work completed on the CLI: openfga/cli#179
On VS Code, this includes:
The text was updated successfully, but these errors were encountered:
tuple_file fields no longer marked invalid as long as file being referenced exists. As of #147
Sorry, something went wrong.
Would definitely be nice to have the second task finished, since I assume it's why we get this warning using the extension:
Reproducible by simply using the FGA CLI testing docs example and moving the tuples to ./tuples.yaml.
./tuples.yaml
Getting the same warning as @mikesouza above.
d-jeffery
No branches or pull requests
Currently, we support a
model_file
option in addition tomodel
for users who prefer to edit their model in a separate file.We should support a
tuple_file
that does the same for tuples.That file will be the same format as accepted by
write
This follows on the work completed on the CLI: openfga/cli#179
On VS Code, this includes:
tuple_file
as invalid, both globally and in testsThe text was updated successfully, but these errors were encountered: