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

Initial reorganization and rewrite of docs #73

Merged
merged 3 commits into from
Sep 18, 2023
Merged

Initial reorganization and rewrite of docs #73

merged 3 commits into from
Sep 18, 2023

Conversation

lkwdwrd
Copy link
Contributor

@lkwdwrd lkwdwrd commented Sep 13, 2023

What code changed, and why?

Since this project is moving beyond the Styra DAS integration with Styra Link to also supporting features in Enterprise OPA, the documentation and general branding needed a bit of a face lift. This renames the plugin to 'Styra VS Code Tools', and reorganizes the README to allow introducing the Enterprise OPA preview integration.

In addition, support has been consolidated into the generally supported SUPPORT.md file, and the developer facing README.md has been consolidated into the CONTRIBUTING.md file.

Lastly, in recognition that we want to fully embrace the name 'Enterprise OPA' for settings, the settings prefixes are updated to render the name more fully and correctly.

Definition of done

Documentation in the extension reflects the overall more general branding and provides information about the new preview features.

How to test

This is not really code to test, but the markdown can be rendered and read through. I highly request this, as there may well be things I missed in proofing the updates.

@lkwdwrd lkwdwrd marked this pull request as ready for review September 14, 2023 19:31
CONTRIBUTING.md Outdated

## Debugging

You can easily launch and debug this extension within VSCode
Copy link
Member

Choose a reason for hiding this comment

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

nit. suggest: You can debug this extension within VSCode.


## Unit Tests

The project boilerplate provides unit tests in a vscode-hosted container of sorts (see /src/tests);
Copy link
Member

Choose a reason for hiding this comment

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

If these tests aren't used or developed, why do we have them?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My guess -- these tests allow for more in depth integration testing with VS Code, and there may have been a goal when this was set up to add some integration testing down the line. However at this point, I am not completely sure.

@lkwdwrd lkwdwrd merged commit c73c276 into main Sep 18, 2023
4 checks passed
@lkwdwrd lkwdwrd deleted the rebrand branch September 18, 2023 17:32
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