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.

Sign up for GitHub

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

Jump to bottom

[Feature] Allow multiple API configs #26

Closed
skoropadas opened this issue Mar 3, 2023 · 1 comment
Closed

[Feature] Allow multiple API configs #26

skoropadas opened this issue Mar 3, 2023 · 1 comment
Assignees
@skoropadas
Labels
Status: Released Type: Enhancement New feature or request

Comments

@skoropadas
Copy link
Member

skoropadas commented Mar 3, 2023 •
edited
Loading

Description

Based on the conversation in #23 ticket, I think it's a good idea to allow multiple API configurations, it could be useful for monorepos or for projects that would like to split the API entities into different pages

Proposed solution

Just start processing multiple API configs and creating a page for each config

Alternatives considered
@skoropadas skoropadas added the Type: Enhancement New feature or request label Mar 3, 2023
@skoropadas skoropadas self-assigned this Mar 3, 2023
skoropadas pushed a commit that referenced this issue Apr 13, 2023
@semantic-release-bot
chore(release): 15.11.0 [skip ci]
b28e7b4 
# [15.11.0](v15.10.5...v15.11.0) (2023-04-13)

### Bug Fixes

* **app:** headings in not indexable content have a wrong margin ([82dbea1](82dbea1))
* **builder:** ng-doc throws an error if a page was removed from the file system ([515e8b7](515e8b7))

### Features

* **builder:** now ng-doc handles several API configuration files correctly ([ab84513](ab84513)), closes [#26](#26)

### Performance Improvements

* **builder:** enable the "noEmit" property for the NgDoc TypeScript project, this should slightly improve performance for the projects with a lot of API entities ([f06a75d](f06a75d))
@github-actions
Copy link

🎉 This issue has been resolved in version 15.11.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@skoropadas skoropadas

Labels
Status: Released Type: Enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@skoropadas