-
Notifications
You must be signed in to change notification settings - Fork 17
Add snippets for annotations and expectations #60
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
Comments
Good idea. It would be nice if you could provide the snippets. You can create them within SQL Developer. They are stored in Based on that I should be able to provide them as part of the utPLSQL extension. I had a quick look at the |
If the utPLSQL framework provides this information, then the it should be possible to update the snippets based on that. However, choosing the right connection to get this information will be challenging, since the preference dialog does not have a connection context. Of course we could add a context menu on the connection to do the snippet update. The question is if we want to support older utPLSQL versions also. If the answer is yes, then we have to provide the snippets as part of the extension (at least for the older utPLSQL versions). |
Hi is a first shot at snippets :) |
Thanks @lwasylow . Good idea to provide a category for annotations and another one for expectations. I think it is even doable to maintain this I plan to include it in the resource folder and provide a button in the preference dialog for the merge with the user's |
Yeah it's small enough to maintain manually and to be fair probably easier. Sounds like good plan |
#60 - add snippets for annotations and expectations
It would be great to have separate Snippet section in SQLDeveloper to aid users.
The snippets could contain a full list of supported annotations and expectations for current version of utPLSQL.
Ideally, utPLSQL framework could include function to provide a list of supported annotations with description and syntax examples.
The text was updated successfully, but these errors were encountered: