Releases: OasisDigital/ng-doc-portal
Releases · OasisDigital/ng-doc-portal
v1.8.0
v1.7.1
v1.7.0
- Added custom landing page provider, allowing uses to override the default content with their own component. This will replace the default message of "Please select a component document page from the side navigation.".
- Added navigation to landing page via title anchor router link. This will take you back to the
/
root route where no component doc page is selected.
v1.6.2
v1.6.1
- Fixed issues with default imports having occurred from upgrading several core packages (prettier, chalk, fastglob, etc...)\
- This issue didn't present itself inside the github repo, but only once published & installed on an actual nx workspace... Should do
npm link
in the future to test before publishing after an upgrade.
- This issue didn't present itself inside the github repo, but only once published & installed on an actual nx workspace... Should do
v1.6.0
- Upgraded to latest Nx & Angular
- Removed prettier as a runtime dependency of the Angular package. We used this to format code for code snippets, but it's main purpose was to make the whitespacing uniform for parsed html/multiline strings. This has been replaced with some logic to uniformly strip leading whitespace across the multiline html/string input. The code passed to the code snippet will not be autoformatted anymore.
- Upgraded as many dependencies as possible to latest (marked, ngx-highlightjs, fast-glob, @phenomnomnominal/tsquery, minimatch etc...)
- minor design fixes of theme select with milligram
v1.5.1
- Swapped to using
prettier/standalone
to optimize purely for browser usages vs. node usages in the code-snippet component. Should hopefully cause less bloat/compilation slowness - Fixed inconsistency of code-snippet component vs. directive input names.
parser
renamed tolang
to match the directivelang
input. - Fixed url in the readme linking to the official package that has all the documentation
v1.5.0
- Made
provideNgDocPortal
that is compatible with Angular's Standalone API's application bootstrapping system.- This syntax uses the same pattern that the native Routing system uses for providing the Router setup/configuration.
- The modules and provider functions are still exposed and around; so, this is backwards compatible with the old module-based system.
- All newly generated
ng-doc-portal
applications will use the Standalone API by default.