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

Comments inside the package/type/view definition so they exist inside the database #66

Merged
merged 2 commits into from
Jul 28, 2017
Merged

Conversation

RamonEsteveCuevas
Copy link
Contributor

@RamonEsteveCuevas RamonEsteveCuevas commented Jul 21, 2017

Fixed the issue #65 with this pull request. Fixed it by first determine if there are comments inside the package body which are comments applying to the object itself. If it exists it moves the comments to the right place for the framework so they can be applied normally. The comments must be within the following format:

create or replace (package/type/view) (force)
  /**
   * Comments which exist inside the database but also in the documentation pages!
   */
(as/is)

Examples can be found in the following directories:
src/packages/subfolder/package_comment_inside_db.pks
src/types/test_type_in_db.tps
src/views/test_view_in_db.vw

Ramon Esteve Cuevas added 2 commits July 21, 2017 12:18
… documentation between. The last one can be parsed by the framework already so no need to change that code. Example can be found inside package (src/packages/subfolder/package_comment_inside_db.pks).

Example:
   create or replace (package/view/type)
    {comments}
   is
to:
  {comments}
  create or replace (package/view/type) is
@martindsouza
Copy link
Member

@RamonEsteveCuevas I've merged it. Please test merged code. Thanks.

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