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

Add render groups support #54

Merged
merged 1 commit into from
May 22, 2019
Merged

Add render groups support #54

merged 1 commit into from
May 22, 2019

Conversation

bceskavich
Copy link
Contributor

Rolodex can now serialize and write docs to multiple targets for a
single Phoenix router. This is helpful for cases where you want
more than one documentation source for a single API (e.g. public and
private API docs).

To accomplish this goal, we're introducing the concept of "render groups".
A render group is a combination of: (optional) filters, a processor, a
writer, and writer options. Together, they encapsulate Rolodex's render
logic: serialization and writing. You can specify as many render groups as
you'd like in your Rolodex config module to generate as many documentation
forms of your API!

@bceskavich bceskavich requested a review from sjkaliski May 21, 2019 18:51
Rolodex can now serialize and write docs to multiple targets for a
single Phoenix router. This is helpful for cases where you want
more than one documentation source for a single API (e.g. public and
private API docs).

To accomplish this goal, we're introducing the concept of "render groups".
A render group is a combination of: (optional) filters, a processor, a
writer, and writer options. Together, they encapsulate Rolodex's render
logic: serialization and writing. You can specify as many render groups as
you'd like in your Rolodex config module to generate as many documentation
forms of your API!
@bceskavich bceskavich merged commit e6fad8c into develop May 22, 2019
@bceskavich bceskavich deleted the bc-render-groups branch May 22, 2019 13:04
@bceskavich bceskavich mentioned this pull request May 22, 2019
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