csf-dev/ZPT-Sharp issues and pull requests

#316 - To improve performance, compile-time code generation should be used for C# expressions

Issue - State: closed - Opened by craigfowler almost 2 years ago - 3 comments
Labels: enhancement, invalid

#315 - Decommission Travis build & set up AppVeyor Linux build

Issue - State: open - Opened by craigfowler over 2 years ago
Labels: bug

#314 - Bump Newtonsoft.Json from 12.0.3 to 13.0.1 in /ZptSharp.Cli

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago
Labels: dependencies

#313 - To learn about them, docs must be written for ZPT elements

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#312 - To learn them, developers should be able to read about the Global Contexts

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#311 - To conform with standards, rename ZptSharp core packages

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs, build/devops

#310 - To automatically add markup, developers must be able to use an interface do so

Issue - State: closed - Opened by craigfowler over 3 years ago - 1 comment
Labels: enhancement

#309 - To avoid premature detail, the conceptual summary should not include METAL, TAL or TALES

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: enhancement, docs

#308 - To learn their usage, developers should be able to read docs about the hosting builders

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#307 - To learn about extending ZptSharp, developers should be able to read docs

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#306 - To learn the syntax, developers should be able to read reference docs

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#305 - To learn ZptSharp, developers should be able to read a tutorial

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#304 - To learn about its usage, docs for the CLI renderer must be written

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#303 - To learn ZptSharp, developers should be able to read a quick-start guide

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#302 - To reduce boilerplate, there should be no need for two-phase registration of services

Issue - State: closed - Opened by craigfowler over 3 years ago - 1 comment
Labels: enhancement, docs

#301 - To introduce the consumption of the API, the intro page must be written

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#300 - So developers can read about them, the ViewEngines page must be written

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#299 - To read about them, a previous versions page must be added to the docs site

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#298 - To read about the available packages, the NuGet packages page must be written

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: docs

#297 - To avoid extra work when only one document provider is enabled, it should be used automatically

Issue - State: closed - Opened by craigfowler over 3 years ago
Labels: enhancement

#296 - To ensure high-priority API documentation is useful, a number of types should be reviewed for docs

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: docs

#295 - To see passing CI builds, the Travis/Linux environment must be fixed

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: bug, build/devops

#294 - To document and smoke-test the MVC Core implementation, a sample project must be created

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement, docs

#293 - To introduce content, a few directories should have README files

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: docs

#292 - For convenient publishing, AppVeyor builds should publish the documentation website

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: enhancement, docs, build/devops

#291 - To allow easier value-filling, developers should be able to use simple replacement values in templates

Issue - State: closed - Opened by craigfowler almost 4 years ago - 3 comments
Labels: invalid

#290 - To clarify the API, in many places, element should be renamed node

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement

#289 - To make build & test easier, tests should target a lower dotnet version

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: enhancement, build/devops, invalid

#288 - To configure ZptSharp, developers should be able to select a default expression type

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: enhancement, invalid

#287 - To find the first and last grouped result, a developer should be able to use 'first' and 'last' variables in a TAL repeat scenario

Issue - State: open - Opened by craigfowler almost 4 years ago - 1 comment
Labels: enhancement

#286 - To support the use of their own XmlUrlResolvers, developers should be able to provide them from config

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement

#285 - To support referencing variables directly in path expressions, a developer should be able to use a 'var' expression type

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement

#284 - When handling a TAL on-error attribute, an error variable must set

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: bug

#283 - To conform with standards, 'global' expressions should be supported

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: bug

#282 - To make repeatable test runs easier, they should be configured with a .runsettings file

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement, build/devops

#281 - To improve performance, path expression evaluation based upon reflection should use a caching mechanism

Issue - State: closed - Opened by craigfowler almost 4 years ago - 2 comments
Labels: enhancement

#280 - To conform with integration tests, the 'string' expression evaluator should also be available using the alias 'str'

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: bug

#279 - To choose desired behaviour, a developer should be able to configure the default TALES expression type

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement

#278 - To automate creation, NuGet packages should be created by AppVeyor

Issue - State: closed - Opened by craigfowler almost 4 years ago - 2 comments
Labels: enhancement, build/devops

#277 - To learn the API, devs should be able to read a generated API docs website

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: docs, build/devops

#276 - To control rendering, all configuration settings must be used/applied

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: enhancement

#275 - To organise & identify assemblies, the build process should write appropriate assembly metadata

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: build/devops

#274 - To analyse branches without impacting on main project stats, SonarCloud should be configured for branch analysis

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: build/devops, spike

#273 - To read a summary of what this repo contains, a README should be added

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement, docs, build/devops

#272 - To determine what needs to be updated, the documentation website should be explored

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: docs, spike

#271 - To reinstate the functionality, the batch rendering mechanism must be restored

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement

#270 - To reinstate the functionality, 'load' expressions must be restored

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: invalid

#269 - To reinstate the functionality, 'csharp' expressions must be restored

Issue - State: closed - Opened by craigfowler almost 4 years ago - 2 comments
Labels: enhancement

#268 - To reinstate the functionality, 'pipe' expressions must be restored

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement

#267 - To use ZptSharp in projects, NuGet packages must be available

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement, build/devops

#266 - To improve reliability, assemblies must be strong-named

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement, build/devops

#265 - To use ZptSharp in apps which do not use DI, a host/factory must be created

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement, docs

#264 - To use ZptSharp from a command line, a standalone app must be created

Issue - State: closed - Opened by craigfowler almost 4 years ago - 3 comments
Labels: enhancement

#263 - To use ZptSharp with ASP.NET Core, an MVC view engine must be created

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: enhancement

#262 - To use ZptSharp with MVC 5 websites, a view engine must be written

Issue - State: closed - Opened by craigfowler almost 4 years ago
Labels: enhancement

#261 - To correctly resolve named XHTML entities, DTD resolution functionality must be restored

Issue - State: closed - Opened by craigfowler almost 4 years ago - 2 comments
Labels: bug

#260 - To verify that it is no longer required (or to restore it), HAP configurations should be revisited

Issue - State: closed - Opened by craigfowler almost 4 years ago - 1 comment
Labels: bug, spike

#259 - ViewBag items do not work with TALES path expressions

Issue - State: closed - Opened by craigfowler about 4 years ago - 2 comments
Labels: bug

#258 - To improve on this library, a general code review should be performed and improvements suggested

Issue - State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking

#257 - To avoid conflicts, CSF libraries should be upgraded to the latest versions

Issue - State: closed - Opened by craigfowler over 4 years ago
Labels: enhancement, breaking, build/devops, do next

#256 - For compatibility, this library should be multi-targeted

Issue - State: closed - Opened by craigfowler over 4 years ago - 2 comments
Labels: enhancement, build/devops

#255 - To publicise its existence, a user should be able to read docs about pipe expressions

Issue - State: closed - Opened by craigfowler over 6 years ago
Labels: enhancement, docs

#254 - To develop plugins separately from core, devs should be able to use the repos as independent projects within an organisation

Issue - State: closed - Opened by craigfowler over 6 years ago - 2 comments
Labels: enhancement, build/devops, invalid

GitHub / csf-dev/ZPT-Sharp issues and pull requests