Issues
- 3
To improve performance, compile-time code generation should be used for C# expressions
#316 opened by craigfowler - 0
- 0
To read about them, a previous versions page must be added to the docs site
#299 opened by craigfowler - 0
- 0
- 0
- 0
To learn them, developers should be able to read about the Global Contexts
#312 opened by craigfowler - 0
- 0
- 0
To learn their usage, developers should be able to read docs about the hosting builders
#308 opened by craigfowler - 0
- 0
- 0
- 3
To allow easier value-filling, developers should be able to use simple replacement values in templates
#291 opened by craigfowler - 1
To automatically add markup, developers must be able to use an interface do so
#310 opened by craigfowler - 1
To reduce boilerplate, there should be no need for two-phase registration of services
#302 opened by craigfowler - 2
To improve performance, path expression evaluation based upon reflection should use a caching mechanism
#281 opened by craigfowler - 0
To avoid extra work when only one document provider is enabled, it should be used automatically
#297 opened by craigfowler - 1
- 0
To avoid premature detail, the conceptual summary should not include METAL, TAL or TALES
#309 opened by craigfowler - 0
To read about the available packages, the NuGet packages page must be written
#298 opened by craigfowler - 0
To support the use of their own XmlUrlResolvers, developers should be able to provide them from config
#286 opened by craigfowler - 1
To determine what needs to be updated, the documentation website should be explored
#272 opened by craigfowler - 0
- 0
To ensure high-priority API documentation is useful, a number of types should be reviewed for docs
#296 opened by craigfowler - 1
For convenient publishing, AppVeyor builds should publish the documentation website
#292 opened by craigfowler - 2
- 0
- 0
- 0
To reinstate the functionality, the batch rendering mechanism must be restored
#271 opened by craigfowler - 0
- 0
To document and smoke-test the MVC Core implementation, a sample project must be created
#294 opened by craigfowler - 0
- 0
To organise & identify assemblies, the build process should write appropriate assembly metadata
#275 opened by craigfowler - 0
To choose desired behaviour, a developer should be able to configure the default TALES expression type
#279 opened by craigfowler - 0
- 1
To learn the API, devs should be able to read a generated API docs website
#277 opened by craigfowler - 0
To make repeatable test runs easier, they should be configured with a .runsettings file
#282 opened by craigfowler - 1
- 0
To support referencing variables directly in path expressions, a developer should be able to use a 'var' expression type
#285 opened by craigfowler - 0
- 0
To conform with integration tests, the 'string' expression evaluator should also be available using the alias 'str'
#280 opened by craigfowler - 0
- 1
To find the first and last grouped result, a developer should be able to use 'first' and 'last' variables in a TAL repeat scenario
#287 opened by craigfowler - 1
To configure ZptSharp, developers should be able to select a default expression type
#288 opened by craigfowler - 2
- 1
- 0
To analyse branches without impacting on main project stats, SonarCloud should be configured for branch analysis
#274 opened by craigfowler - 0
- 0